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.

Quality

72%

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 ./agent/src/skills/commodity-analysis/SKILL.md

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.

The body is a well-structured, information-dense analytical framework with concrete code, tables, and an output template. Main gaps are non-executable code literals and inlined reference material that could be externalized.

Suggestions

Make the Python snippets valid and runnable (replace '90%'/'5%' literals with 0.90/0.05 and define or comment input variables) so examples are copy-paste ready.

Add an explicit validation/verification step to the five-step framework (e.g., cross-check the composite signal against term structure and macro before emitting a direction).

Consider moving the per-commodity seasonality calendars and data-source tables into reference bundle files linked from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is dense and domain-specific (tables, code, factor weights) with little generic padding that Claude already knows; a few explanatory prose chains and the Notes section could be trimmed, keeping it just below the lean anchor 5.	4 / 5
Actionability	Provides concrete Python signal snippets, data-source tables, a composite-scoring template, and a copy-paste output format; not a 5 because code uses invalid literals (e.g. '90%', '5%') and undefined input variables, so it is not directly copy-paste executable.	4 / 5
Workflow Clarity	The five-step analysis framework is clearly sequenced with confirm/validate steps (term structure 'confirms' supply-demand; macro 'validation' as step 5); this is a research skill so the destructive/batch cap does not apply, but explicit verification checkpoints are only implicit.	4 / 5
Progressive Disclosure	Well-organized with clear section headers and no nested references, but it is a single ~200-line file with reference-like content (seasonality calendars, data-source tables) inlined rather than split into bundle files, so it sits below the well-split anchor 5.	4 / 5
	Total	16 / 20 Passed

Description

70%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 and distinctive, naming a clear commodity-analysis niche with concrete sub-capabilities and a defined output. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks about commodity direction, oil/gold/copper outlook, supply-demand balance, inventory cycles, or futures term structure.'

Frame the parenthetical sub-domains as concrete actions (e.g., 'analyze supply-demand balance, model gold pricing, track inventory cycles') to lift specificity from topic-listing to action-listing.

Include common synonyms (crude oil, precious metals, term structure, roll yield) to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the commodity-analysis domain and enumerates six concrete sub-capabilities (oil supply-demand, gold pricing, copper predictor, inventory cycles, futures premium-discount, seasonality) plus the action 'generating directional commodity signals'; not a 5 because sub-domains are framed as topics rather than discrete actions and backtesting is omitted.	4 / 5
Completeness	The 'what' is clear (multi-dimension commodity analysis yielding directional signals), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms a user would say (oil, gold, copper, supply-demand, inventory cycles, futures, seasonality, commodity signals), but misses common synonyms (crude oil, precious metals, term structure) and any explicit trigger phrasing, so it is below the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (commodity directional signals across oil/gold/copper with named analytical dimensions) with distinct triggers and minimal overlap risk against other analysis skills.	5 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: HKUDS/Vibe-Trading
Path: agent/src/skills/commodity-analysis/SKILL.md
Commit: 99e84ab

Reviewed: 1 day 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.