CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-copilot-provider

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

52

Quality

57%

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

Fix and improve this skill with Tessl

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

Quality

Content

61%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 content is well-structured with concrete, executable commands and clear auth precedence, but it repeats cost/quota points across sections and lacks explicit validation checkpoints on the dispatch workflow. As a single-file integration spec it is navigable and actionable with modest trimming opportunities.

Suggestions

Dedupe the "zero additional cost" and "premium request quota" points so they appear once (e.g., only in Integration Notes) to tighten conciseness.

Add an explicit detect -> auth-check -> dispatch -> verify-output sequence with a validation checkpoint for the dispatch step to raise workflow clarity.

Move the full example-workflow ASCII blocks and the multi-provider indicator legend into a short reference or keep only a single representative example inline to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes competence (no basic concept explanations), but "zero additional cost" and "premium request" are repeated across the Overview, Core principle, and Integration Notes, leaving more than minor tightening to do.

3 / 5

Actionability

Copy-paste-ready commands are provided (copilot -p, copilot login, export token, detection snippet, model pinning), with only minor gaps such as no combined detect-then-dispatch example and an isolated "return 0" detection block.

4 / 5

Workflow Clarity

The auth precedence list and detection-then-degradation flow are clearly sequenced, but the dispatch path lacks explicit validation checkpoints (e.g., verify provider output, handle non-zero exit) and the workflow steps are implicit rather than enumerated.

3 / 5

Progressive Disclosure

The single self-contained file is well organized with clear section headers and no nested references, though the full example-workflow blocks and the provider-indicator legend are inlined content that could be split out for a 5.

4 / 5

Total

14

/

20

Passed

Description

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

The description is specific and distinct but omits explicit "when to use" trigger guidance, which lives in the frontmatter trigger block instead of the description text. Specificity and completeness are therefore capped at 3 despite a clearly distinguishable niche.

Suggestions

Add a "Use when..." clause directly in the description (e.g., "Use when the user asks to add or enable the Copilot provider") so the description itself answers when to activate.

List one or two more concrete capabilities in the description (e.g., "dispatch research prompts", "report Copilot auth status") to lift specificity from 1-2 actions toward several.

Fold the strongest natural trigger phrases ("copilot provider", "github copilot") into the description rather than relying solely on the separate trigger block.

DimensionReasoningScore

Specificity

Names the tool and one concrete mechanism ("copilot -p programmatic mode") but does not list multiple specific actions, fitting the "1-2 concrete actions" anchor rather than the "several actions" anchor above.

3 / 5

Completeness

A clear "what" (optional zero-cost provider via copilot -p) is present but there is no "Use when..." trigger guidance in the description field itself, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

The description includes the natural term "GitHub Copilot" but the rich trigger phrases ("copilot provider", "add copilot") live in the separate trigger block, not the description; coverage is partial rather than comprehensive.

3 / 5

Distinctiveness Conflict Risk

The named tool plus specific programmatic mode carves a clear niche with minor overlap risk, though the description alone lacks explicit distinct trigger phrases needed for a 5.

4 / 5

Total

13

/

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
nyldn/claude-octopus
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.