geopolitical-risk

Geopolitical risk analysis: quantify crisis signals, identify precursors, and build event-driven strategies for war, sanctions, and supply disruption scenarios.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./agent/src/skills/geopolitical-risk/SKILL.md

Quality

Content

63%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 rich, largely executable geopolitical-risk skill with strong domain content, concrete code, and a clear phased workflow. Its weaknesses are monolithic structure with no progressive disclosure and a length that exceeds what a SKILL.md overview should carry.

Suggestions

Split the body into one-level-deep reference files (e.g., HOTSPOTS.md, ASSET_MAPPING.md, DATA_SOURCES.md) and keep SKILL.md as a concise overview with clearly signaled links, to raise progressive_disclosure.

Trim or externalize the per-hotspot structural repetition and verbose docstrings to tighten conciseness toward a lean overview.

Add explicit validation/feedback steps in the data and backtest workflows (e.g., verify the GPR download succeeded and columns exist before computing signals) to push workflow_clarity toward 5.

Dimension	Reasoning	Score
Conciseness	The 916-line body is information-dense and largely avoids explaining concepts Claude already knows, but the sheer volume and per-hotspot structural repetition could be tightened or moved out, so it is not a 4.	3 / 5
Actionability	Provides mostly executable, copy-paste-ready Python (load_gpr_index, gpr_signal, oil_war_premium, query_gdelt_events, portfolio_stress_test) with specific tickers and URLs; minor gaps remain in illustrative functions (crisis_vol_strategy) and placeholder constants ('your@email.com', beta estimates 'should be updated').	4 / 5
Workflow Clarity	Clear phased sequence (Phase 1 positioning, Phase 2 trading, Phase 3 mean reversion) reinforced by the GREEN/YELLOW/ORANGE/RED signal levels and checklists; lacks explicit validate-then-retry feedback loops in the data workflows, keeping it below 5.	4 / 5
Progressive Disclosure	Well-organized with clear section headers, but it is a monolithic single file with no bundle/reference files; large blocks (six hotspot deep-dives, asset-class mappings, data-source APIs) are inlined rather than split into one-level-deep references.	3 / 5
	Total	14 / 20 Passed

Description

78%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 strong, domain-specific description that names concrete actions and distinct trigger scenarios in third person. Its main weakness is the absence of an explicit 'Use when...' trigger clause and slightly abstract action verbs.

Suggestions

Add an explicit trigger clause such as 'Use when the user asks about war, sanctions, trade conflict, or supply disruption scenarios' to lift completeness toward 5.

Sharpen the action verbs from abstract ('quantify crisis signals', 'identify precursors') to more concrete operations (e.g., 'score GPR Index signals', 'map asset-class shocks').

Include a few more natural synonyms users say ('conflict', 'trade war', 'tensions') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('quantify crisis signals', 'identify precursors', 'build event-driven strategies') with minor coverage gaps; the actions are somewhat more abstract than the 'extract text / fill forms' exemplar, so it sits below a 5.	4 / 5
Completeness	Clearly states the 'what' (quantify, identify, build strategies) and embeds a 'when' via 'for war, sanctions, and supply disruption scenarios', but lacks an explicit 'Use when the user mentions...' trigger phrase, so it is not a 5.	4 / 5
Trigger Term Quality	Good natural keyword coverage ('war', 'sanctions', 'supply disruption', 'crisis', 'geopolitical risk') that users would actually say; a few common synonyms are missing (e.g., 'conflict', 'trade war', 'tariffs'), keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (geopolitical risk analysis) with distinct scenario triggers (war, sanctions, supply disruption) that are unlikely to collide with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (917 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: HKUDS/Vibe-Trading
Path: agent/src/skills/geopolitical-risk/SKILL.md
Commit: e90b6c6

Reviewed: ~12 hours 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.