AB substack-news
Scrape AI-related articles from Substack search using browser automation. Uses agent-browser to render Substack's JS-dependent search page, extract titles, authors, and summaries, and format them as a numbered digest. Use when: (1) user asks to search Substack for articles or news, (2) user wants recent Substack posts on any topic, (3) user mentions "Substack" + a search term + "articles/posts/news". NOT for: general web search, fetching a single Substack post by URL.
As a process B 67/100 · Nearly there — weak spots: inputs and preconditions, consistency, progress reporting
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 · 0
✓ No critical or high findings
Files scanned: 4. 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 67/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (substack-news) differs from the folder (substack-search)
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 75Steps. 3 steps
- 100Tools and files. No external tools needed
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 265 tokens
- 100Running it twice. No mutating operations
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
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 472: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 3 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 100.