CC competitive-intel-watch
Scheduled delta monitoring against a prior competitive snapshot. Use when tracking competitors on a cadence: material shifts only, cited evidence, battle-card update flags, runs unattended.
Scheduled delta monitoring against a prior competitive snapshot.
As a process C 60/100 · Has gaps — References files that are not bundled: ../autonomous-investigation/SKILL.md, ../intelligence-collection-disciplines/SKILL.md, ../competitive-research-snapshot/SKILL.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../autonomous-investigation/SKILL.md - warning
missing-refreference to a missing file: ../intelligence-collection-disciplines/SKILL.md - warning
missing-refreference to a missing file: ../competitive-research-snapshot/SKILL.md - warning
missing-refreference to a missing file: ../battle-card-builder/SKILL.md - warning
missing-refreference to a missing file: ../pestel-analysis/SKILL.md - note
frontmatter-keyunknown frontmatter key "intent" - note
frontmatter-keyunknown frontmatter key "type" - note
frontmatter-keyunknown frontmatter key "theme" - note
frontmatter-keyunknown frontmatter key "best_for" - note
frontmatter-keyunknown frontmatter key "scenarios" - note
frontmatter-keyunknown frontmatter key "estimated_time"
Process rating: all ten parameters 60/100
- 0Tools and files. 5 referenced file(s) missing: ../autonomous-investigation/SKILL.md, ../intelligence-collection-disciplines/SKILL.md, ../competitive-research-snapshot/SKILL.md
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 55Failures and branches. 1 branches
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 38 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2323 tokens
- low 11 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)
- +1No license
- +2Single-language instructions
- +3Description length 189: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 38 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.