AB ptt-bbs
Scrape PTT web BBS (https://www.ptt.cc) with Python requests + BeautifulSoup — no login required. Covers every public web feature: hot board list, board category tree, board article lists, board search (keywords, author:, thread:, recommend:), single articles with exact push (推) / boo (噓) / neutral (→) counts and score (推 − 噓), board-wide push totals, and the essence area (精華區). Use this whenever the user mentions PTT, ptt.cc, Taiwanese BBS boards (Gossiping, NBA, Stock, ...), 推文/噓文 counts, 精華區, or wants to crawl/search/analyze PTT articles or comments — even if they don't say "scrape" explicitly.
Scrape PTT web BBS (https://www.ptt.cc) with Python requests + BeautifulSoup — no login required. Covers every public web feature: hot board list, board…
As a process B 67/100 · Nearly there — weak spots: inputs and preconditions, running it twice, 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Scrape PTT web BBS (https://www.ptt.cc) with Python requests + Bea… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
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
- 30Running it twice. 17 mutating operations with no state check
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 19 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1838 tokens
- low The response is described with custom markup (5 tags): a typed call is more reliable
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 604: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 19 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.