CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

contrarian-setup-gate

Synthesize the three Jason Shapiro contrarian-pipeline verdicts (COT crowding, news-reaction failure, weekly price-action confirmation) into one actionable setup_status via a fail-closed precedence state machine. Pure, offline synthesis -- no network, no API keys, no computation beyond validation and precedence.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/contrarian-setup-gate/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 highly actionable, well-sequenced skill body with copy-paste-ready commands, exhaustive outcome handling, and a properly signaled one-level-deep reference structure. The main weakness is conciseness: several pockets of implementation-spec detail (vintage validation, non-finite scanning, reserved-enum notes) are inlined in the body where they dilute the operational guidance.

Suggestions

Move the Prerequisites vintage-validation paragraph (run_context/markets data_date validation, legacy fallbacks, first-10-character parsing compatibility) into references/gate-decision-table.md -- the script performs this validation automatically, so the operator-facing Prerequisites only needs the input requirements.

Trim Guardrail 3 to the rule statement (non-finite values anywhere in a report fail closed with reason <input>_non_finite) and move the scan mechanics (1e309 overflow, Infinity/NaN literals, iterative whole-file scan) to the reference's existing non-finite section.

Cut changelog-style asides from the body, e.g. "not yet built as of this skill's release" and the LOW-is-reserved-but-never-emitted parenthetical, leaving one-clause versions or moving them to the reference.

DimensionReasoningScore

Conciseness

The status table, output contract, and CLI example all earn their tokens, but there is unnecessary spec-level explanation that could be tightened: the Prerequisites vintage-validation paragraph ("Existing first-10-character date parsing remains compatible; this is not a stricter full-timestamp or provenance-schema validator" reads like changelog notes), Guardrail 3's extended non-finite-scan detail ("an ordinary-looking number like 1e309 that overflows on parse... ANYWHERE in it"), and the LOW-confidence parenthetical in Step 3. Mostly efficient with some unnecessary explanation rather than only minor instances, so it sits below anchor 4.

3 / 5

Actionability

Fully executable guidance: a copy-paste-ready CLI command with all flags and example values, explicit flag semantics ("omit either to see the state at that pipeline stage"), a status table mapping every outcome to a concrete next action, and a complete output contract. The common cases (full run and partial pipeline stages) are both covered, matching the top anchor.

5 / 5

Workflow Clarity

Clear three-step sequence with explicit validation semantics (asymmetric exit behavior: exit 2 for operator error, exit 0 with a fail-closed named-reason report for bad input), a feedback loop for error recovery ("fix or regenerate the named input before rerunning"), and per-status next actions for all five statuses. The operation is a read-only synthesis gate, not destructive or batch, so the validation cap does not apply.

5 / 5

Progressive Disclosure

Good structure with a well-signaled, verified one-level-deep reference ("See references/gate-decision-table.md for the full decision table... the reason-token glossary, and worked examples") plus a Resources section describing every bundle file; all referenced paths exist and the reference contains no nested references. Minor organization gap: the vintage-validation spec in Prerequisites and the non-finite-scan detail in Guardrail 3 are inlined implementation detail that belongs in the reference, keeping it below the cleanly-split top anchor.

4 / 5

Total

17

/

20

Passed

Description

66%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.

A precise, domain-specific description that clearly states what the skill does and its operating constraints, with strong niche keywords. Its main weakness is the absence of any explicit "Use when..." trigger guidance, which caps completeness and leaves the invocation context implied rather than stated.

Suggestions

Add an explicit trigger clause, e.g. "Use after running cot-contrarian-detector (and optionally news-reaction-failure-analyzer and technical-analyst's contrarian-confirmation mode) when you need the combined setup status for a symbol."

Name the three upstream sibling skills (cot-contrarian-detector, news-reaction-failure-analyzer, technical-analyst) in the description so users referencing those skill names naturally trigger this gate.

State the input/output medium explicitly -- reading the three report JSON files and writing a gate report -- to round out the what-coverage now left implicit.

DimensionReasoningScore

Specificity

Names concrete inputs ("COT crowding, news-reaction failure, weekly price-action confirmation"), a concrete output ("one actionable setup_status"), and the mechanism ("fail-closed precedence state machine") with operating constraints ("no network, no API keys"). Falls between anchor 3 and anchor 5: more precise than 1-2 generic concrete actions, but it describes a single synthesis action rather than comprehensive multi-action coverage, and reading/writing the report files is left implicit.

4 / 5

Completeness

The "what" is clear (synthesize three verdicts into one setup_status), but there is no "Use when..." clause or equivalent explicit trigger guidance; the "when" is only weakly implied through pipeline context. Per the rubric guideline, a missing 'Use when...' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage for the niche: "contrarian", "COT crowding", "news-reaction failure", "price-action", "setup_status", "Jason Shapiro". A few natural terms are missing -- the upstream sibling skill names (cot-contrarian-detector, news-reaction-failure-analyzer, technical-analyst) that pipeline users would naturally say -- so it stops short of anchor 5's comprehensive synonym-level coverage.

4 / 5

Distinctiveness Conflict Risk

Clear niche -- the synthesis gate that combines verdicts, distinct from detection or analysis -- but it shares concept keywords ("COT crowding", "news-reaction", "price-action") with its three upstream sibling skills, creating minor overlap risk with closely related skills. Not 5: shared vocabulary could pull triggers intended for the upstream skills; not 3: the synthesize-into-setup_status action clearly distinguishes it from generic overlap.

4 / 5

Total

15

/

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

Path

skills/contrarian-setup-gate/SKILL.md

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.