CC consulting-analysis
Use this skill when the user requests to generate, create, or write professional research reports including but not limited to market analysis, consumer insights, brand analysis, financial analysis, industry research, competitive intelligence, investment due diligence, or any consulting-grade analytical report. This skill operates in two phases — (1) generating a structured analysis framework with chapter skeleton, data query requirements, and analysis logic, and (2) after data collection by other skills, producing the final consulting-grade report with structured narratives, embedded charts, and strategic insights.
Use this skill when the user requests to generate, create, or write professional research reports including but not limited to market analysis, consumer…
As a process C 62/100 · Has gaps — References files that are not bundled: Actual_File_Path, path, URL
The same skill appears in 1 more place: RA-Skills
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 8197 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: Actual_File_Path - warning
missing-refreference to a missing file: path - warning
missing-refreference to a missing file: URL - warning
missing-refreference to a missing file: chart_file_path
Process rating: all ten parameters 62/100
- 0Tools and files. 4 referenced file(s) missing: Actual_File_Path, path, URL
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 40Execution cost. Instruction body is 8197 tokens: crowds the task out of the window
- 60Steps. 132 steps, 8 vague phrases
- 60Result and completion. Output format stated, no completion criterion
- 100When it triggers. States when to use and when not to
- 100Inputs and preconditions. Inputs and preconditions are listed
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- low 18 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 623: enough signal without eating the budget
- +4Structure: 56 headings
- +3Step-by-step instructions: 132 items
- +3Output format is stated explicitly
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.