AB editorial-topic-portfolio
This skill should be used when evaluating a portfolio of technology, AI, data, cloud, or enterprise-software content topics. It normalizes Notion or Markdown/JSON/CSV inputs, applies factual, timeliness, originality, argument-capacity, positioning, and privacy gates, scores eligible topics, selects one primary and two backups, produces merge/watch/covered/abandon decisions, and prepares a confirmed Notion writeback preview. By default, it never writes to Notion without two explicit confirmations; a workspace with a documented standing instruction to sync every routine review may use that instruction as the authorization, but must still generate a change preview and perform readback verification. 中文触发词: 选题评估, 选题组合, 竞争密度, 原创空间, Notion选题库, 内容排期
This skill should be used when evaluating a portfolio of technology, AI, data, cloud, or enterprise-software content topics.
As a process B 73/100 · Nearly there — weak spots: 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: 18. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "description_zh" - note
frontmatter-keyunknown frontmatter key "description_en" - note
frontmatter-keyunknown frontmatter key "not_for" - note
frontmatter-keyunknown frontmatter key "agent_created" - note
frontmatter-keyunknown frontmatter key "read_when"
Process rating: all ten parameters 73/100
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (editorial-topic-portfolio) differs from the folder (editorial-topic-portfolio-skill)
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 101 steps
- 100Execution cost. Instruction body is 2660 tokens
- 100Running it twice. Mutating operations check current state
- low 10 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 751: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 101 items
- +3Output format is stated explicitly
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
- +3All 4 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.