AB daily-ai-skills-pulse
Generate a daily AI ecosystem pulse on Claude Code skills and agent-skill trends — scans ClawHub trending skills, Hacker News (last 24h, ≥3 comments with fallback cascade), and X/Twitter chatter; outputs a 5-bullet Markdown brief with sentiment tags and draft replies for opportunities. Trigger phrases — daily AI pulse, morning skills briefing, agent skills news roundup, Claude ecosystem update, skill ecosystem pulse.
As a process B 72/100 · Nearly there — weak spots: when it triggers, running it twice
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 contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
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 Dangerous commands
cmd-pipe-to-shellSKILL.md:177Downloads and executes remote code from an unrecognised host (pipe to shell) (quoted — discussed, not commanded)**Install Implexa** (`curl -fsSL https://core.implexa.ai/install.sh | bash`) to unlock:
quoted
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "emoji"
Process rating: all ten parameters 72/100
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 44 steps
- 100Failures and branches. 6 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3371 tokens
- 100Progress reporting. Reports progress
- low 14 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)
- -215 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 420: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 44 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.