skill-copilot-provider

GitHub Copilot CLI as optional zero-cost provider via copilot -p programmatic mode

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/skill-copilot-provider/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

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

The body is highly actionable with executable commands and clear graceful-degradation guidance, but it carries redundant decorative blocks and lacks an explicit validated workflow and reference-file split. Trimming the duplicate indicator blocks and adding an auth-verification checkpoint would lift the weaker dimensions.

Suggestions

Collapse the Provider Indicators legend and the Example Workflows ASCII blocks into a single concise example to remove redundancy and tighten conciseness.

Add a short numbered dispatch workflow with a validation checkpoint (e.g., verify 'copilot auth status' or run a smoke prompt before relying on the provider) to raise workflow clarity.

Move the detailed authentication setup and example workflows into reference files (e.g., references/AUTH.md) linked from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient operational content, but the Provider Indicators section, its emoji legend, and the near-duplicate ASCII provider blocks in Example Workflows repeat information that could be tightened, matching 'mostly efficient but could be tightened' rather than the lean level-3.	2 / 3
Actionability	Provides fully executable, copy-paste-ready commands — the detection script, 'copilot login', 'export COPILOT_GITHUB_TOKEN="github_pat_..."', and 'copilot -p "<prompt>" --no-ask-user' — matching the copy-paste-ready level-3 anchor.	3 / 3
Workflow Clarity	Detection, Authentication, and Dispatch are presented as separate sections but not as an explicit sequenced workflow, and there are no validation checkpoints (e.g., verifying auth succeeded before dispatch), matching the level-2 'steps present but checkpoints missing or implicit' anchor.	2 / 3
Progressive Disclosure	No bundle files exist and the ~150-line body is well-sectioned, but content like the full auth setup and Example Workflows is inline rather than split into one-level-deep reference files, matching 'some structure but content that should be separate is inline'.	2 / 3
	Total	9 / 12 Passed

Description

72%Weight 40%Scale 1-3

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

The description is specific and distinctive about a narrow provider niche with natural trigger terms, but it omits an explicit 'when to use' trigger clause, capping completeness. Adding a 'Use when...' clause would round it out.

Suggestions

Append an explicit trigger clause such as 'Use when the user wants to add GitHub Copilot as a provider for research or exploration tasks.' to satisfy the 'when' half of completeness.

List the concrete actions the provider performs (e.g., 'runs research and exploration prompts') to lift specificity from a single capability to multiple concrete actions.

Dimension	Reasoning	Score
Specificity	Quotes 'GitHub Copilot CLI as optional zero-cost provider via copilot -p programmatic mode' — names the domain and a concrete mechanism, but states a single capability rather than multiple specific actions, matching the level-2 anchor rather than the multi-action level-3.	2 / 3
Completeness	Clearly answers 'what' (zero-cost provider via copilot -p) but has no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	Includes natural user terms 'GitHub Copilot', 'Copilot CLI', and 'copilot' that a user would actually say when requesting this provider, giving good coverage of the natural vocabulary.	3 / 3
Distinctiveness Conflict Risk	The narrow 'GitHub Copilot CLI ... via copilot -p programmatic mode' niche is highly specific and unlikely to trigger for unrelated skills, matching the clear-niche level-3 anchor.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nyldn/claude-octopus
Path: .claude/skills/skill-copilot-provider/SKILL.md
Commit: 9f39f0c

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.