CtrlK
BlogDocsLog inGet started
Tessl Logo

scenario-analyzer

Skill that analyzes 18-month scenarios from a news headline. Runs the primary analysis with the scenario-analyst agent and obtains a second opinion with the strategy-reviewer agent. Generates a comprehensive English report covering 1st/2nd/3rd-order impacts, recommended stocks, and a critical review. Example: /scenario-analyzer "Fed raises rates by 50bp" Triggers: news analysis, scenario analysis, 18-month outlook, medium-to-long-term investment strategy

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable orchestrator skill with clear sequencing and correctly split references; the main weakness is redundancy across the Important Notes, Output, and Step 3.3 sections.

Suggestions

Consolidate the output-save-location rule: state it once (e.g. in Step 3.3) and reference it from the Output table and Important Notes instead of repeating the path and example multiple times.

Remove the duplicated probability-allocation and second-opinion-is-mandatory statements from Important Notes since they already appear in the agent prompt and Quality Checklist.

Trim the ASCII architecture diagram or the repeated event-type examples if they restate content already covered in the Workflow phase descriptions.

DimensionReasoningScore

Conciseness

The body is mostly efficient and actionable, but several rules are repeated across sections — the output-save location restated in Step 3.3, the Output table, and Important Notes (with a second example), and probability/second-opinion rules re-stated in Important Notes and the checklist — so it could be tightened.

2 / 3

Actionability

Provides copy-paste-ready guidance: exact `subagent_type` values with full prompt templates, a concrete save path `reports/scenario_analysis_<topic>_YYYYMMDD.md`, and a complete report markdown template.

3 / 3

Workflow Clarity

The process is clearly sequenced into Phase 1/2/3 with sub-steps and ends with a Quality Checklist verification step; the operations are not destructive/batch, so absent validate→fix loops do not cap the score.

3 / 3

Progressive Disclosure

Orchestration logic lives inline while detailed material is split into three real, one-level-deep reference files (`headline_event_patterns.md`, `sector_sensitivity_matrix.md`, `scenario_playbooks.md`) that are clearly signaled in both the workflow and a Resources section.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific, third-person description that covers concrete capabilities, natural trigger terms, and explicit when-to-use guidance with a distinct niche.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "analyzes 18-month scenarios", "Runs the primary analysis with the scenario-analyst agent", "obtains a second opinion", "Generates a comprehensive English report covering 1st/2nd/3rd-order impacts, recommended stocks" — matching the score-3 anchor for multiple specific concrete actions.

3 / 3

Completeness

It explicitly answers "what" (the analysis/agent/report actions) and "when" via an explicit "Triggers:" clause plus an invocation example, satisfying both halves required for a 3.

3 / 3

Trigger Term Quality

The "Triggers:" clause surfaces natural user phrasings — "news analysis, scenario analysis, 18-month outlook, medium-to-long-term investment strategy" — giving good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

The 18-month news-headline investment-scenario niche with named agents is a clear, distinct trigger set unlikely to collide with other skills; voice is third person ("Runs", "Generates").

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tradermonty/claude-trading-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.