CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

code-mate-github-copilot

Run GitHub Copilot CLI non-interactively for coding tasks. Use when the user asks to delegate work to Copilot.

Quality

89%

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

100%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.

An exemplary lean, single-purpose skill body: exact executable commands, pre-flight and failure checkpoints, explicit safety guardrails, and a concrete worked example, all in about two dozen lines with zero padding. No material weaknesses found against the rubric.

DimensionReasoningScore

Conciseness

Every sentence is operational ("set a finite timeout, normally 10 minutes", "the published exit-code contract is incomplete", "Never request, read, print, or copy credentials") with no padding and no explanation of concepts Claude already knows. It matches the lean 5-anchor; I could not identify tokens that fail to earn their place, so the 4-anchor's 'minor instances of over-explanation' does not apply.

5 / 5

Actionability

The guidance is copy-paste ready: `command -v copilot` for the pre-check, the exact command `copilot -p "<prompt>" -s --output-format json --no-ask-user`, explicit failure semantics ("treat an error event or nonzero exit as failure"), and a worked example (explain a failing test without modifying files) covering the common case. The only gap — no example `--allow-tool` entry — is a deliberately narrow secondary path, which keeps it at 5 rather than dropping to 4.

5 / 5

Workflow Clarity

A clear 3-step sequence with explicit validation checkpoints: availability check with stop-and-ask on failure, error-event/nonzero-exit failure detection, and auth-failure handling. The simple-skill exception applies (single unambiguous action, under 50 lines) and the skill is neither destructive nor batch, so the cap does not bind; no actual validation gap remains for the 4-anchor.

5 / 5

Progressive Disclosure

The body is under 50 lines, contains no bundle files and references none (the references/scripts/assets directories do not exist), and is organized into two well-labeled sections (Run, Authentication And Permissions). This matches the guideline that short skills with no need for external references score 5 with well-organized sections.

5 / 5

Total

20

/

20

Passed

Description

73%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 concise, third-person description that clearly states what the skill does and gives an explicit 'Use when' trigger with a distinctive Copilot-pinned niche. Its main weakness is thin capability and trigger coverage — one action and one trigger formulation rather than a fuller enumeration.

Suggestions

Enumerate the concrete coding tasks Copilot is delegated to (e.g., explain failing tests, review diffs, propose fixes) to raise specificity from one action to several.

Broaden the when-clause with additional natural trigger phrasings, e.g. 'Use when the user asks to delegate work to Copilot, mentions Copilot, or asks Copilot to do a coding task'.

State the non-interactive result contract in the description (e.g., 'returns JSONL output for summarizing') so the what covers how results are consumed.

DimensionReasoningScore

Specificity

"Run GitHub Copilot CLI non-interactively for coding tasks" names the domain and one concrete action (run non-interactively) but does not list several specific actions, matching the anchor for 1-2 concrete actions without comprehensive coverage. It is above a bare domain mention ('Processes PDF files') because 'non-interactively' and the delegation framing add real capability detail.

3 / 5

Completeness

Both parts are explicit: the what ("Run GitHub Copilot CLI non-interactively for coding tasks") and the when ("Use when the user asks to delegate work to Copilot"). It matches the 4-anchor rather than 5 because the when-clause is a single trigger formulation that could be more explicit and specific with additional concrete trigger phrases.

4 / 5

Trigger Term Quality

Natural terms users would say are present: "Copilot", "GitHub Copilot CLI", and "delegate work to Copilot" give good keyword coverage for this niche. It falls short of the 5-anchor because coverage is not comprehensive — no synonyms or phrasing variations like 'asks Copilot to do a task' or 'pair programming'.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche pinned to GitHub Copilot ("Run GitHub Copilot CLI", "delegate work to Copilot") with distinct triggers and minimal conflict risk — no other plausible skill would trigger on delegating to Copilot. The 4-anchor's 'minor overlap risk' does not apply.

5 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

CherryHQ/cherry-studio

Path

resources/code-cli-skills/code-mate-github-copilot/SKILL.md

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.