CtrlK
BlogDocsLog inGet started
Tessl Logo

copilot-sdk

This skill helps with GitHub Copilot SDK work across Node.js/TypeScript, Python, Go, .NET, and Java. It covers setup, authentication, permissions, streaming events, custom tools, custom agents, MCP servers, hooks, skills, and session persistence.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/copilot-sdk/skills/SKILL.md

The canonical home for this skill is copilot-sdk in intellectronica/agent-skills

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 a well-organized, mostly lean reference with a concrete quick-start example, clear cross-language mappings, and genuine one-level-deep reference files. Main improvements would be tightening the redundant inline fact sections and adding explicit validation/error-recovery steps to the quick-start workflow.

Suggestions

Consolidate overlapping inline content ("High-value facts" vs "Core capabilities to remember") to reduce token cost and redundancy.

Add an explicit validation/verification step to the quick-start workflow (e.g. verify `session.idle` arrived and check `getStatus()` before `disconnect()`), with an error-recovery branch.

Provide at least a minimal runnable snippet per language or clearly point each language to the matching section in references/working-examples.md from the convention table.

DimensionReasoningScore

Conciseness

The body is dense and factual with no padding about concepts Claude already knows, though the ~40-line link list and some overlap between "High-value facts" and "Core capabilities to remember" could be trimmed, placing it just below a 5.

4 / 5

Actionability

A copy-paste-ready TypeScript quick-start example, install commands, a language-convention table, and per-language permission-handler mappings give concrete executable guidance, but only one language has a full runnable example while others are delegated to reference files, leaving minor gaps.

4 / 5

Workflow Clarity

The "Quick start pattern" gives a clear six-step sequence (create client, create session with permission handler, register handlers, send, wait for session.idle, disconnect/stop), but explicit validation checkpoints and error-recovery feedback loops are mostly implicit rather than spelled out.

4 / 5

Progressive Disclosure

The SKILL.md serves as an overview with four well-signaled one-level-deep references (event-system, cli-agents-mcp, working-examples, troubleshooting, all real files), but the sizable inline "High-value facts" and "Core capabilities to remember" sections keep it just shy of an ideally split overview.

4 / 5

Total

16

/

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 clearly communicates the skill's scope across five languages and many capability areas, but it lacks an explicit "Use when..." trigger clause, capping completeness. Tightening the generic verbs ("helps with"/"covers") into concrete actions would raise specificity.

Suggestions

Add an explicit trigger clause, e.g. "Use when working with the GitHub Copilot SDK (copilot-sdk) across Node.js/TypeScript, Python, Go, .NET, or Java."

Replace the generic verbs "helps with" and "covers" with concrete actions like "Set up, authenticate, and drive Copilot SDK sessions, register custom tools/agents/MCP, handle streaming events, and persist sessions."

Include natural synonyms or package names (e.g. "copilot-sdk", "@github/copilot-sdk") to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain and lists a comprehensive set of capability areas ("setup, authentication, permissions, streaming events, custom tools, custom agents, MCP servers, hooks, skills, and session persistence"), but the verbs "helps with" and "covers" are less concrete than action verbs, so it sits just below a 5.

4 / 5

Completeness

The "what" is clearly stated (SDK work across five languages covering ten areas), but there is no "Use when..." clause or equivalent trigger guidance, which the guidelines cap at 3.

3 / 5

Trigger Term Quality

"GitHub Copilot SDK" plus the five language names are natural terms a user would say, giving good keyword coverage, though a few synonyms (e.g. "copilot-sdk", "programmatic Copilot") and file extensions are absent.

4 / 5

Distinctiveness Conflict Risk

"GitHub Copilot SDK" is a clear niche with distinct triggers and minimal conflict risk, though minor overlap exists with broader Copilot or CLI skills.

4 / 5

Total

15

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
intellectronica/agent-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.