BC pilot-media-monitoring-setup
Deploy a media monitoring and intelligence platform with 4 agents. Use this skill when: 1. User wants to set up coordinated media crawling, sentiment analysis, trend detection, and reporting agents 2. User is configuring a brand monitoring, share-of-voice tracking, or PR crisis detection workflow 3. User asks about media intelligence pipelines, sentiment scoring, or automated media briefings Do NOT use this skill when: - User wants a single RSS or news feed (use pilot-stream-data instead) - User wants to send a one-off Slack notification (use pilot-slack-bridge instead) - User only needs event filtering without the full pipeline (use pilot-event-filter instead)
Deploy a media monitoring and intelligence platform with 4 agents.
As a process C 56/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Bash
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 56/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
- 30Running it twice. 1 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 4 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1461 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
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 669: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 4 items
- +4Has examples (7 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.