BC knowledge-connector
Knowledge workbench connector. Input notes, documents, or a local knowledge folder; output import guidance, relationship maps, cross-document answers, and concrete next actions. Privacy boundary: do not upload sensitive notes unless the user explicitly chooses an external tool.
As a process C 64/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, running it twice
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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-tokenpackage-lock.json:71High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…FSj+bWLt…2sH/Kn8E…h6w==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:182High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…Loy/Rxalv2kr+lqMlUnrDWV+3j4p…IHu+HtC7…g8A==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:203High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…CpK+FtMRQVdIMN6/Df5j…tIC+7KYK…qaA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:327High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha512-l+sSef…kmC+4EH2…jvA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:340High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…q1F+ppbRo70+YeaD…NPN+GD6b…CXQ==",
detector
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 64/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 41 steps
- 100Failures and branches. 4 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1020 tokens
- 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)
- +1No license
- +2Single-language instructions
- +3Description length 278: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 41 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.