AC offlyn-clipper
Use when the user mentions Offlyn Clipper, Clipper notes, meetings, voice notes, live meeting, current meeting, catch me up, catch-up, what did I miss, recap this call, search my notes, prior thinking, or /offlyn-clipper. You HAVE live-meeting support via MCP tool clipper_catch_me_up while Clipper is recording on this Mac. NEVER say live meeting integration is missing or not in your skill list—call clipper_catch_me_up or clipper_list_chat_presets first. Also use clipper_search_notes for saved notes and clipper_get_note_context for a specific note ID.
Use when the user mentions Offlyn Clipper, Clipper notes, meetings, voice notes, live meeting, current meeting, catch me up, catch-up, what did I miss, recap…
As a process C 62/100 · Has gaps — weak spots: result and completion, inputs and preconditions
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenmcp-bridge/package-lock.json:75High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…GLi+2W/6ao+6Y7gu/RCwR…Kng==",
detector -
low Secrets in code
secret-high-entropy-tokenmcp-bridge/package-lock.json:254High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…GLw+xYSd…cqA==",
detector -
low Secrets in code
secret-high-entropy-tokenmcp-bridge/package-lock.json:309High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…FrF+LTRo…W3g==",
detector -
low Secrets in code
secret-high-entropy-tokenmcp-bridge/package-lock.json:318High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…A6j+hAmM…GbS+kf5c…csw==",
detector -
low Secrets in code
secret-high-entropy-tokenmcp-bridge/package-lock.json:375High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…F4j+6INO…yXw==",
detector
Files scanned: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 62/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 85Steps. 14 steps, 1 vague phrases
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1054 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
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
- +1No license
- +2Single-language instructions
- +3Description length 556: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 14 items
- +4Has examples (8 code blocks)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.