CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

onboard-plugin

Scaffold a new plugin and prepare it for distribution. WHEN: 'create a new plugin', 'scaffold a new plugin'

Quality

81%

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

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

A strong, command-driven workflow that covers the full plugin onboarding lifecycle with concrete, executable steps, an explicit test checkpoint, and well-signaled external references. Minor improvements are possible: reduce repeated location/command scaffolding, add a fix-and-retry loop after the integration test, and move the optional separate-workflow setup into a reference file.

DimensionReasoningScore

Conciseness

The body is efficient and almost entirely repo-specific procedural knowledge Claude cannot know (scaffold commands, hooks fragments, telemetry patterns, pinned-SHA guidance), with no padding explaining known concepts. It sits at score 4 rather than 5 due to minor trimmable redundancy, e.g. the "cd scripts" blocks each duplicate the "# At <repo-root>/scripts/" location comments and the plugin-name instruction is repeated across sections.

4 / 5

Actionability

Every step is a copy-paste-ready command with explicit working directories ("npm i", "npm run plugin:new -- --plugin {plugin-name}", "npm run build", "npm run test:vally -- --plugin {plugin-name} --skill {skill-name}"), including a failure path ("If it fails, ask the skill author to report a bug to microsoft/github-copilot-for-azure"). This matches score 5's fully executable, common-case-covering anchor; score 4 would require minor gaps in the commands, which are absent.

5 / 5

Workflow Clarity

The sequence is clear and well-ordered (install deps → scaffold plugin → scaffold skills → build → run integration test → prepare release → finish implementation) with an explicit checkpoint: "The test should pass. If it fails, ask the skill author to report a bug." It stops short of score 5 because the failure path defers to bug reporting rather than a validate-fix-retry loop, and there is no verification that scaffolded files were created before proceeding to the test step.

4 / 5

Progressive Disclosure

Sections are well organized and external material is appropriately deferred via clearly signaled, one-level-deep references ("Refer to the `Plugin Structure` section of [Onboarding.md]", "Follow [skill-authoring]", "Follow [vally-eval]") — matching score 4's good structure with minor gaps. It is not score 5 because the ~25-line "Set up a separate integration test workflow" optional section is inlined detail that would fit better in a reference file.

4 / 5

Total

17

/

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 with an explicit WHEN clause containing natural trigger phrases, giving it strong completeness and distinctiveness. Its main weakness is specificity: only one truly concrete action is stated and "prepare it for distribution" glosses over the actual onboarding workflow.

Suggestions

Replace or expand "prepare it for distribution" with the concrete steps the skill actually performs, e.g. "Scaffold a new plugin, generate its skills and integration tests, and prepare it for release."

Add trigger variations users might naturally say, such as "onboard a plugin", "add a new plugin", or "set up a new plugin".

Mention the repo context (scaffolding plugins in this repository) so the scope is unambiguous to the trigger-matching reader.

DimensionReasoningScore

Specificity

"Scaffold a new plugin" is a concrete action, but the second half "prepare it for distribution" is generic, matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It is above score 2 because the domain (plugin scaffolding) is named with a real action, but below score 4 because it does not list several specific actions (e.g., no mention of scaffolding skills, running integration tests, or setting up codeowners).

3 / 5

Completeness

It explicitly answers both what ("Scaffold a new plugin and prepare it for distribution") and when ("WHEN: 'create a new plugin', 'scaffold a new plugin'"), placing it above score 3's weak/missing 'when'. It falls short of score 5 because the 'what' is thin — "prepare it for distribution" is vague and the richer onboarding steps (scaffold skills, run integration tests, finish implementation) never appear.

4 / 5

Trigger Term Quality

The WHEN clause offers two natural phrases users would actually say: "'create a new plugin', 'scaffold a new plugin'" — good keyword coverage matching score 4's 'a few natural terms missing'. It is below score 5 because common variations like "onboard a plugin", "add a new plugin", or "set up a plugin" are absent.

4 / 5

Distinctiveness Conflict Risk

Plugin scaffolding is a clear niche and the two trigger phrases are distinct, unlikely to fire for unrelated skills — matching score 5's 'clear niche with distinct triggers; minimal conflict risk'. Score 4 would require observable overlap with a closely related skill, which the description does not exhibit.

5 / 5

Total

16

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 6 suspicious

Warning

Total

15

/

16

Passed

Repository

microsoft/GitHub-Copilot-for-Azure

Path

.github/skills/onboard-plugin/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.