CC Explain
Keeps the principal current on the fundamentals of what is going on in the principal's projects, work and technical infrastructure: spoken interactive lessons on the conversation topic, deep explanations of an area's fundamentals read fresh from live sources, and quizzes that remember what the principal missed. USE WHEN teach me, /tm, /teach-me, tutorial, teach me this, walk me through this interactively, learn mode, quiz me, help me actually understand what we just did, explain fundamentals, /ef, what are the fundamentals of, how does this project actually work, catch me up on, refresh me on, quiz fundamentals, /qf, quiz me on the fundamentals, test what I know about, am I still current on. NOT FOR elaborating my last answer (the elaborate shortcut), the LifeOS core pitch (lc), story explanations of content (StoryExplanation), designed visual maps (Visualize), discovery interviews on a half-formed idea (/discuss).
Keeps the principal current on the fundamentals of what is going on in the principal's projects, work and technical infrastructure: spoken interactive lessons…
As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- 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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 9, column 14: description: Keeps the principal current on the fundamentals of what is going o… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens)
Process rating: all ten parameters 57/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 50When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 5 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 833 tokens
- 100Running it twice. No mutating operations
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
- +3Description length 928: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +4Structure: 5 headings
- +3Step-by-step instructions: 5 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.