SKILLEMALL.ai

BB copilot-cli-quickstart

Use this skill when someone wants to learn GitHub Copilot CLI from scratch. Offers interactive step-by-step tutorials with separate Developer and Non-Developer tracks, plus on-demand Q&A. Just say "start tutorial" or ask a question! Note: This skill targets GitHub Copilot CLI specifically and uses CLI-specific tools (ask_user, sql, fetch_copilot_cli_documentation).

github/awesome-copilot Agent Skills author: github MIT 1 file body ≈ 7 102 tokens Open the sourcegithub.com analyzed 13 h ago

Offers interactive step-by-step tutorials with separate Developer and Non-Developer tracks, plus on-demand Q&A.

As a process B 70/100 · Nearly there — weak spots: result and completion, inputs and preconditions

IntegrationGitHubLearningtype and topics are labelled automatically from the skill text
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
72
Run on models
none yet
Process rating
B
70/100
Nearly there
Result and completion w 14
0
Inputs and preconditions w 11
0
When it triggers w 12
70
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: RA-Skills

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 7102 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 70/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 70When it triggers. States when to use, but not when not to
  • 70Execution cost. Instruction body is 7102 tokens
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 95 steps
  • 100Failures and branches. 13 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 14 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -2209 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +3Description length 367: enough signal without eating the budget
  • +4Structure: 40 headings
  • +3Step-by-step instructions: 95 items
  • +4Has examples (28 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.