CtrlK
BlogDocsLog inGet started
Tessl Logo

stanley-druckenmiller-investment

Druckenmiller Strategy Synthesizer - Integrates 8 upstream skill outputs (Market Breadth, Uptrend Analysis, Market Top, Macro Regime, FTD Detector, VCP Screener, Theme Detector, CANSLIM Screener) into a unified conviction score (0-100), pattern classification, and allocation recommendation. Use when user asks about overall market conviction, portfolio positioning, asset allocation, strategy synthesis, or Druckenmiller-style analysis. Triggers on queries like "What is my conviction level?", "How should I position?", "Run the strategy synthesizer", "Druckenmiller analysis", "総合的な市場判断", "確信度スコア", "ポートフォリオ配分", "ドラッケンミラー分析".

70

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

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

A well-engineered meta-skill body: fully executable orchestration command, prerequisite validation with a remediation loop, and excellently signaled one-level-deep references. It loses points on token efficiency — the trigger list, skill roster, and scoring weights are each stated twice — and on navigation completeness, since the assets template and supporting scripts are invisible from the body.

Suggestions

Trim the bilingual 'When to Use This Skill' section (and the 'Relationship to Other Skills' table) — the frontmatter description already carries the triggers and the Input Requirements tables already carry the skill roster; keep only the time-horizon column as a note.

Move the 7-Component Scoring, 4 Pattern, and Conviction Zone tables into a reference file (e.g., conviction_matrix.md) and keep only a one-line summary in the body, since the script computes these values itself.

Add an explicit failure-handling step to Phase 2 (e.g., what to do if the script exits non-zero or reports are stale beyond --max-age), and mention assets/strategy_report_template.md and the supporting scripts/ modules in a bundle-layout note so all shipped files are discoverable.

DimensionReasoningScore

Conciseness

The body is mostly tight, table-driven prose with no explanations of concepts Claude already knows, but it carries real redundancy: the 16-line bilingual "When to Use" section restates the frontmatter's trigger list verbatim, the "Relationship to Other Skills" table re-lists all eight skills already tabulated under Input Requirements, and the 7-component weight / pattern / conviction-zone tables (~45 lines) restate implementation details the script computes. This fits anchor 3 ('mostly efficient but includes some unnecessary content that could be tightened') better than anchor 4's 'minor instances'.

3 / 5

Actionability

The Phase 2 command is complete and copy-paste ready — "python3 skills/stanley-druckenmiller-investment/scripts/strategy_synthesizer.py --reports-dir reports/ --output-dir reports/ --max-age 72" with all flags specified — and the doc enumerates exact output filenames ("druckenmiller_strategy_YYYY-MM-DD_HHMMSS.json/.md") and the seven post-run steps the script performs, matching the fully-executable 5 anchor.

5 / 5

Workflow Clarity

The four phases are clearly sequenced with an explicit prerequisite checkpoint and recovery path ("Check that the 5 required skill JSON reports exist... and are recent (< 72 hours). If any are missing, run the corresponding skill first"), fitting anchor 4; it stops short of anchor 5 because there is no guidance for handling a failed or malformed synthesizer run (e.g., what to do if the script errors or emits no output).

4 / 5

Progressive Disclosure

All four references (investment-philosophy.md, market-analysis-guide.md, case-studies.md, conviction_matrix.md) are real one-level-deep files, each introduced with a summary and an explicit load condition, plus a "When to Load References" decision table — near anchor 5. It drops to 4 because the scoring/pattern/zone spec tables duplicate script internals inline instead of living in a reference, and the body never mentions the assets/strategy_report_template.md or the other scripts/ modules that the bundle ships.

4 / 5

Total

16

/

20

Passed

Description

96%Weight 40%Scale 1-5

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

An exemplary description: it states precisely what the skill does with quantified outputs, names all eight upstream inputs, and provides explicit bilingual 'Use when' triggers including literal example queries. The only weakness is that a few of the broadest triggers (positioning, asset allocation) could also fire for the sibling analysis skills it orchestrates.

DimensionReasoningScore

Specificity

"Integrates 8 upstream skill outputs (Market Breadth, Uptrend Analysis, Market Top, Macro Regime, FTD Detector, VCP Screener, Theme Detector, CANSLIM Screener) into a unified conviction score (0-100), pattern classification, and allocation recommendation" names every input and three concrete, quantified outputs — comprehensive concrete-action coverage matching the 5 anchor, well above anchor 4's 'minor gaps'.

5 / 5

Completeness

Both halves are explicit: the 'what' is the integration into a conviction score, pattern classification, and allocation recommendation, and the 'when' is a literal "Use when user asks about..." clause followed by concrete trigger queries — the exact shape of the 5 anchor example; a missing trigger clause would have capped it at 3, but it is present.

5 / 5

Trigger Term Quality

"What is my conviction level?", "How should I position?", "Run the strategy synthesizer", plus domain synonyms ("overall market conviction, portfolio positioning, asset allocation, strategy synthesis") and Japanese equivalents ("確信度スコア", "ポートフォリオ配分") give exhaustive coverage of natural user phrasings, matching the 5 anchor's synonym-inclusive standard.

5 / 5

Distinctiveness Conflict Risk

Niche triggers like "Run the strategy synthesizer" and "Druckenmiller analysis" are clearly distinct, but broader triggers such as "How should I position?" and "portfolio positioning, asset allocation" overlap with the eight closely related sibling analysis skills named in the same description — fitting anchor 4 ('minor overlap risk with closely related skills') rather than 5's minimal-conflict standard.

4 / 5

Total

19

/

20

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.

Validation — 16 / 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.