Agent skill

candidate-evaluation

Evaluate GitHub contributors for MLOps/engineering roles. Use when analyzing candidates, researching GitHub profiles, or updating CONTRIBUTORS.md with hiring assessments.

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill candidate-evaluation-pollinations-pollinations-2 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 3 KB
Bundled scripts: none
Allowed tools: ReadWriteEditGrepBash(ghapi:*)Bash(git:*)
Path: skills/analysis/candidate-evaluation-pollinations-pollinations-2/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Candidate Evaluation Skill Evaluate GitHub contributors for engineering roles at Pollinations. ## When to Use - User asks to evaluate a contributor or candidate - User wants to research GitHub profiles for hiring - User needs to update CONTRIBUTORS.md with candidate analysis - User mentions "hiring", "candidate", "MLOps", or "evaluate contributor" ## Evaluation Criteria ### Must-Have Skills (Weight: High) - **Python**: Primary language proficiency - **DevOps**: Docker, CI/CD, infrastructure - **GPU/ML Deployment**: Model serving, inference optimization ### Nice-to-Have Skills (Weight: Medium) - Kubernetes, vLLM, TGI - Quantization (GGUF, ONNX) - CI/CD pipelines (GitHub Actions) ### Work Style Indicators (Weight: Medium) - PR size preference (small, focused = good) - Response time to reviews - Documentation quality - Test coverage habits ## Evaluation Process 1. **Gather Data** via GitHub MCP or `gh api`: ```bash # Get user repos gh api users/{username}/repos --jq '.[].name' # Search PRs in pollinations gh api search/issues -X GET -f q='repo:pollinations/pollinations author:{username}' # Search code for MLOps keywords gh api search/code -X GET -f q='user:{username} docker OR kuber

What's inside
Steps it walks through
  1. When to Use
  2. Evaluation Criteria
  3. Must-Have Skills (Weight: High)
  4. Nice-to-Have Skills (Weight: Medium)
  5. Work Style Indicators (Weight: Medium)
  6. Evaluation Process
  7. Output Format
  8. Skills Matrix Format
  9. Reference Files
  10. Example Queries
Ships with 1 file
  • metadata.json
Commands it runs
gh api users/{username}/repos --jq '.[].name'
gh api search/issues -X GET -f q='repo:pollinations/pollinations author:{username}'
gh api search/code -X GET -f q='user:{username} docker OR kubernetes OR gpu OR vllm'
More from claude-skill-registry
All skills →
About this skill
What does the candidate-evaluation skill do?

Evaluate GitHub contributors for MLOps/engineering roles. Use when analyzing candidates, researching GitHub profiles, or updating CONTRIBUTORS.md with hiring assessments.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill candidate-evaluation-pollinations-pollinations-2 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going