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

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

85%

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

The body is highly actionable with a clear, well-validated workflow and clean progressive disclosure to real reference files; its main weakness is verbosity in the precedence and guardrail prose.

Suggestions

Tighten the Precedence summary and guardrail #3 by replacing run-on sentences with short bullets, removing repeated restatements of the fail-closed philosophy.

Move the lengthy non-finite-scan rationale out of guardrail #3 into the referenced decision table or a short note, keeping the guardrail to its one-line invariant.

Dimension	Reasoning	Score
Conciseness	Substantive and free of basic-concept filler, but the precedence prose and guardrail #3 use long run-on sentences and repeat the fail-closed rationale, so it could be noticeably tightened.	2 / 3
Actionability	Provides a fully executable CLI invocation with concrete flags and paths plus an exact YAML output contract and a status-to-next-step table -- copy-paste ready.	3 / 3
Workflow Clarity	A clearly sequenced three-step workflow with pervasive explicit validation (fail-closed on every input, defensive invariant check, documented exit codes) and error-recovery guidance.	3 / 3
Progressive Disclosure	The body is an overview that signals one-level-deep references to real bundle files (gate-decision-table.md, the two scripts), appropriately externalizing the large decision table.	3 / 3
	Total	11 / 12 Passed

Description

67%

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 and highly distinctive, clearly stating what the skill does, but it omits explicit 'when to use' trigger guidance and relies on technical jargon over natural user keywords.

Suggestions

Append an explicit 'Use when ...' clause naming the trigger situations (e.g., after running the three contrarian-pipeline steps and needing a single setup_status).

Add natural-language trigger terms a user would actually say (e.g., 'contrarian setup', 'fade the crowd', 'pipeline status') alongside the technical jargon.

Lead with the actionable outcome (produce a setup_status) before the design rationale (fail-closed precedence state machine) to keep the trigger scannable.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions -- synthesize three verdicts into a setup_status via a fail-closed precedence state machine, plus validation and precedence -- rather than vague domain description.	3 / 3
Completeness	Clearly answers 'what' (synthesize verdicts into a setup_status) but provides no explicit 'Use when...' trigger guidance, capping completeness at 2 per the rubric.	2 / 3
Trigger Term Quality	Contains relevant domain keywords (contrarian, COT crowding, setup_status) but they lean technical; it lacks natural user-sayable trigger phrasing and common variations.	2 / 3
Distinctiveness Conflict Risk	A sharply defined niche synthesizing three named upstream skills' reports via a unique precedence state machine, making conflict with other skills very unlikely.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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
Commit: 62a1635

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.