AC ecosystem-mapper
Map the supply chain ecosystem of a given industry — identify upstream/midstream/downstream/horizontal-support positions and representative companies at each. Use when user asks for '生态图谱', '供应链分析', 'industry ecosystem map', '产业图谱', '行业生态', '产业链'. Outputs markdown with 4-生态位 breakdown + Mermaid diagram. Part of the industry-analyzer plugin (6-Skill 流水线第 2 环).
Map the supply chain ecosystem of a given industry — identify upstream/midstream/downstream/horizontal-support positions and representative companies at each.
As a process C 57/100 · Has gaps — weak spots: when it triggers, failures and branches, consistency
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: 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 57/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (ecosystem-mapper) differs from the folder (industry-analyzer-ecosystem)
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 40 steps
- 100Execution cost. Instruction body is 529 tokens
- 100Running it twice. No mutating operations
- 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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 361: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 40 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.