CtrlK
BlogDocsLog inGet started
Tessl Logo

copilot-sdk

Build applications that programmatically interact with GitHub Copilot. The SDK wraps the Copilot CLI via JSON-RPC, providing session management, custom tools, hooks, MCP server integration, and streaming across Node.js, Python, Go, and .NET.

56

Quality

65%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/copilot-sdk/SKILL.md

The canonical home for this skill is copilot-sdk in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

65%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 highly actionable with executable multi-language examples and thorough config reference, but it is token-heavy due to four-language repetition and lacks progressive disclosure into separate files and validation checkpoints in its workflows. Some filler (verbatim description, vague 'When to Use') should be trimmed.

Suggestions

Move bulk per-language API examples and full configuration tables into reference files (e.g., reference/node.md, reference/python.md) and keep SKILL.md an overview with one-level-deep links.

Add validation/feedback steps for risky operations (e.g., verify a resumed session exists before send, confirm permission-denial behavior) to raise workflow clarity.

Remove the verbatim description repeat after the frontmatter and replace the vague 'When to Use' filler with concrete trigger guidance.

DimensionReasoningScore

Conciseness

The body is mostly efficient concrete reference material with no basic-concept padding, but it repeats the frontmatter description verbatim, includes a filler 'When to Use' line, and reproduces every feature in four languages, which is token-heavy and could be tightened.

3 / 5

Actionability

The skill is packed with copy-paste-ready code in Node.js, Python, Go, and .NET, plus install commands and configuration tables that cover the common cases comprehensively.

5 / 5

Workflow Clarity

The 'Client → Session → Message' core pattern and auth priority order provide a clear sequence, but there are no validation checkpoints or feedback loops for risky operations such as session destroy/delete or tool-permission denial.

3 / 5

Progressive Disclosure

Section headers and tables give reasonable in-file structure, but with no bundle files present the entire ~500-line reference (per-language examples, full config tables, API summary) is inlined in SKILL.md rather than split into one-level-deep reference files.

3 / 5

Total

14

/

20

Passed

Description

66%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 gives a clear, specific account of what the SDK does across multiple runtimes, but omits any explicit "Use when..." trigger guidance, which limits its completeness and trigger discoverability. It is distinct and largely free of fluff.

Suggestions

Append an explicit 'Use when...' clause naming natural trigger phrases (e.g., building Copilot-powered apps, automating Copilot, integrating Copilot via SDK).

Rewrite capability lists as concrete verbs (e.g., 'manage sessions, define custom tools, intercept hooks') to lift specificity from 4 toward 5.

Add a couple of natural synonyms or file/keyword variations (e.g., 'API', 'CLI automation', 'Copilot integration') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists several concrete capability areas ("session management, custom tools, hooks, MCP server integration, and streaming") across four runtimes, but phrases them as abstract noun-lists rather than vivid concrete verbs, leaving minor gaps.

4 / 5

Completeness

The "what" is clear (wraps Copilot CLI via JSON-RPC, providing enumerated capabilities), but there is no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Strong natural terms like "GitHub Copilot", "SDK", "MCP", "hooks", and "streaming" are present, but common variations such as "API", "automation", or "CLI scripting" are missing.

4 / 5

Distinctiveness Conflict Risk

The GitHub Copilot SDK niche is mostly distinct with clear triggers, but BYOK provider support (OpenAI/Anthropic/Ollama) creates minor overlap risk with general API/SDK skills.

4 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (517 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.