CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

65

Quality

82%

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

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

An exemplary skill body: executable commands, an exact output contract, a well-sequenced workflow with validation checkpoints, and clean deferral of the exhaustive decision table to a single real reference file. The only weakness is minor verbosity in a few guardrail and edge-case asides.

DimensionReasoningScore

Conciseness

The body is dense and skill-specific with no explanations of concepts Claude already knows, but a few overlong parenthetical asides (e.g. the LOW-token reservation note in Step 3 and the overflow example in Guardrail 3) could be trimmed.

4 / 5

Actionability

Provides a copy-paste-ready CLI invocation with all flags, explicit exit-code semantics, a precise YAML output contract, and a status-to-next-step table, fully covering the common case.

5 / 5

Workflow Clarity

The three workflow steps are clearly sequenced with explicit fail-closed validation, documented exit behavior, and a fix-and-rerun feedback loop via INSUFFICIENT_EVIDENCE naming the input to regenerate.

5 / 5

Progressive Disclosure

The body keeps only a precedence summary and defers the full decision table to the real one-level-deep references/gate-decision-table.md (verified to exist), with scripts listed and described in Resources.

5 / 5

Total

19

/

20

Passed

Description

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

The description is specific, distinctive, and honest about scope (offline, no API keys), but it omits any explicit "when to use" trigger guidance and lacks natural trigger variations. Adding a Use-when clause naming the upstream skills and their report files would raise both completeness and trigger quality.

Suggestions

Append a "Use when..." clause naming the triggering moments, e.g. "Use when cot-contrarian-detector, news-reaction-failure-analyzer, or technical-analyst contrarian-confirmation reports exist for a symbol and a setup_status is needed."

Include the natural trigger phrases users of this pipeline would say, such as the upstream skill names (cot-contrarian-detector, news-reaction-failure-analyzer) and report-file patterns (detector JSON, news-reaction report), to broaden keyword coverage beyond the verdict vocabulary.

Optionally split the single composite action into named capabilities (e.g. "validates and combines report JSONs, applies precedence rules, emits setup_status with fail-closed reasons") for fuller specificity coverage.

DimensionReasoningScore

Specificity

"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" names the domain and several concrete operations, but it is one composite action rather than a comprehensive list of separate capabilities, so it falls below the anchor-5 example.

4 / 5

Completeness

The "what" is clear (synthesize three verdicts into one setup_status offline), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Terms like "COT crowding", "contrarian", and "price-action confirmation" are natural for this pipeline's users, but the description offers no synonyms, variations, or trigger phrasing (e.g. "Use when the detector and analyzer reports are ready"), matching the anchor for some relevant keywords with missing variations.

3 / 5

Distinctiveness Conflict Risk

"Jason Shapiro contrarian-pipeline verdicts", "fail-closed precedence state machine", and "setup_status" carve out a clear niche with triggers that would not plausibly fire any other skill.

5 / 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
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.