CtrlK
BlogDocsLog inGet started
Tessl Logo

commodity-analysis

Commodity analysis (oil supply-demand balance / gold pricing / copper as an economic predictor / inventory cycles / futures premium-discount structure / seasonality), generating directional commodity signals.

60

Quality

75%

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 ./agent/src/skills/commodity-analysis/SKILL.md
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 high-quality, information-dense analysis skill body: nearly all content is domain knowledge Claude cannot be assumed to know (thresholds, data sources, weights, signal mappings), organized into a clear five-step workflow with cross-validation steps and a concrete output template. Its only real costs are minor over-explanation of familiar concepts, pseudocode-style signal snippets, and a monolithic single-file layout at ~200 lines.

Suggestions

Trim or drop definitions Claude already knows (contango/backwardation parentheticals, 'negative real rates mean negative holding cost') to tighten token efficiency.

Add brief guidance on what to do when the validation steps disagree (e.g., supply-demand bullish but term structure in deep contango) to close the workflow's feedback-loop gap.

Consider moving the per-commodity indicator and seasonality tables into one-level-deep reference files (e.g., references/oil.md, references/gold.md, references/copper.md) so SKILL.md stays a lean overview.

DimensionReasoningScore

Conciseness

The body is dense with domain-specific value (data sources, thresholds, weights, signal mappings) presented as tables and short snippets, not prose padding. Minor over-explanations of things Claude already knows — e.g., 'Contango (futures > spot, normal market)' and 'negative real rates mean negative holding cost' — keep it just below the lean anchor of 5.

4 / 5

Actionability

Concrete, executable guidance throughout: exact thresholds ('TC < $30/ton = tight', 'spread_ratio > 0.02'), a weighted four-factor gold model, a composite scoring template, and a fill-in output format. Not a 5 because the Python snippets use undefined variables (opec_compliance, china_import_yoy) and are explicitly 'simplified', though the skill does honestly note data must be retrieved externally.

4 / 5

Workflow Clarity

The five-step framework is clearly sequenced (supply-demand → inventory → term structure → seasonality → macro) with built-in validation checkpoints — step 3 'confirms the supply-demand judgment' and step 5 validates against macro, plus a note to cross-check lagged inventory with price/basis behavior. Not a 5 because there is no explicit disagreement-handling guidance for when validation steps contradict each other.

4 / 5

Progressive Disclosure

Well-organized single-file structure with clear section headers and a coherent overview → concepts → framework → output flow; no bundle files exist and no references are buried. Not a 5 because at ~200 lines the per-commodity detail (e.g., seasonality tables, commodity-specific indicator tables) is arguably inline content that could be split into one-level-deep reference files, which the ideal anchor rewards.

4 / 5

Total

16

/

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 specific, information-dense description that clearly names its domain and six concrete analytical dimensions plus a defined output. Its main weakness is the complete absence of any 'when to use' trigger guidance, which caps completeness and slightly weakens trigger quality.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user asks about commodities, oil/gold/copper outlooks, inventory or term-structure analysis, or wants directional commodity signals.'

Include common synonyms users actually say — 'crude oil', 'WTI/Brent', 'futures curve/term structure' — to broaden natural trigger coverage.

State the output artifact more concretely (e.g., 'outputs a composite-scored commodity report with direction and confidence') to sharpen the 'what'.

DimensionReasoningScore

Specificity

The description lists several specific analysis dimensions — 'oil supply-demand balance / gold pricing / copper as an economic predictor / inventory cycles / futures premium-discount structure / seasonality' — plus a concrete output ('generating directional commodity signals'). Not a 5 because it names analysis topics rather than multiple concrete actions, and coverage of the framework's actual outputs (composite scoring, trading direction) is partial.

4 / 5

Completeness

The 'what' is clear (multi-dimension commodity analysis producing directional signals), but there is no 'Use when...' clause or any explicit trigger guidance — when to invoke the skill is entirely missing, which caps completeness at 3 per the judging guidelines. It is a solid 3 rather than a 2 because the 'what' is unusually detailed.

3 / 5

Trigger Term Quality

Good natural keyword coverage ('commodity', 'gold pricing', 'copper', 'inventory cycles', 'seasonality') that a user asking for commodity or oil/gold/copper analysis would plausibly say. A few natural terms are missing (e.g., 'crude oil', 'WTI', 'Brent', 'futures curve'), keeping it below the comprehensive synonym/extension coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

The commodity/macro niche with distinctive triggers ('copper as an economic predictor', 'futures premium-discount structure') is mostly distinct with minimal conflict risk. Not a 5 because generic phrases like 'commodity analysis' and 'macro' framing could overlap with general market-analysis or macro-economics skills.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
HKUDS/Vibe-Trading
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.