CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-academy-stargazers

Look up who has starred the microsoft/agent-academy repository on GitHub. Use this skill whenever the user wants to check stargazers, see if a specific GitHub user has starred the repo, or retrieve an up-to-date list of stargazers. Trigger whenever the user says "who starred agent academy", "check stargazers", "has <user> starred the repo", or asks anything about the repository's stargazer list. This skill uses the GitHub CLI to fetch stargazers via the GitHub API and saves the results to a local JSON file. It will install prerequisites if needed.

67

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured and actionable with a clear gated workflow and error handling. It loses points mainly to redundancy between the Rules and Prerequisites sections and a key command given in prose rather than verbatim.

Suggestions

Give the full stargazers command verbatim (e.g., `gh api repos/microsoft/agent-academy/stargazers --paginate --jq '[.[] | {login, type, url}]'`) so it is copy-paste ready.

Remove the prerequisite/install/auth steps duplicated between Prerequisites and Rules, referencing the Prerequisites section once instead.

Add an explicit verification step after saving (e.g., confirm temp/stargazers.json is non-empty/valid JSON) to close the workflow feedback loop.

DimensionReasoningScore

Conciseness

Mostly efficient and free of concept over-explanation, but the Rules section duplicates the Prerequisites (install gh, gh auth login) and re-states pagination details already covered in the flow, so it could be tightened.

3 / 5

Actionability

Provides concrete, executable commands (gh --version, gh auth status, the --jq filter, save path), but the full gh api command with the repo endpoint is described in prose rather than given as a copy-paste-ready line.

4 / 5

Workflow Clarity

Clear numbered sequence with a prerequisite gate ("Do not proceed until both checks pass") and explicit error handling, but lacks an explicit verify/feedback step confirming the saved file is valid.

4 / 5

Progressive Disclosure

A short, single-purpose skill with well-organized sections (Prerequisites, Skill Flow, Rules) and no need for external references, meeting the simple-skill bar for full marks.

5 / 5

Total

16

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states what the skill does and when to use it, with natural trigger phrases and a narrow, low-conflict niche. The only minor gap is a few missing trigger-term variations.

DimensionReasoningScore

Specificity

Names multiple concrete actions — look up stargazers, check whether a specific user starred the repo, fetch via the GitHub CLI/API, save to a local JSON file, and install prerequisites — giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what (look up stargazers, check a user, save to JSON) and when with concrete trigger phrases ("Use this skill whenever…", "Trigger whenever the user says…").

5 / 5

Trigger Term Quality

Includes natural phrases a user would say ("who starred agent academy", "check stargazers", "has <user> starred the repo") plus synonyms (stargazers/starred), but a few common variations are missing, so it sits just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Targets stargazers of a single named repo (microsoft/agent-academy) with distinct triggers, giving it a clear niche and minimal overlap with other skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
microsoft/agent-academy
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.