CtrlK
BlogDocsLog inGet started
Tessl Logo

osint-investigation

Follow the money via public records and sanctions data.

56

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/research/osint-investigation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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, highly actionable pipeline with strong progressive disclosure and disciplined validation/evidence rules. Its only real weakness is the absence of an explicit validate-fix-retry feedback loop, which keeps workflow_clarity at 4.

DimensionReasoningScore

Conciseness

The body is dense and information-rich, assumes Claude's competence (no explaining what OSINT or sanctions are), and uses executable commands over prose. Minor padding remains (the 'Adapted from' note and repeated rate-limit guidance in step 2 and the Tools section), so it stops short of a 5.

4 / 5

Actionability

Every step ships copy-paste-ready bash commands with real flags, file paths, and documented output CSV columns, and entity-resolution/timing examples cover the common cases. It is not a 4 because there are no meaningful gaps in executability.

5 / 5

Workflow Clarity

Five clearly numbered steps form a coherent pipeline (sources -> acquire -> resolve -> timing -> findings) with validation behaviors (0-row warnings, confidence tiers, p-value discipline, idempotent re-runs). It is not a 5 because there is no explicit validate-then-fix-then-retry gate loop of the form the rubric's anchor-5 example shows, even though validation is otherwise well handled.

4 / 5

Progressive Disclosure

SKILL.md is a workflow overview that points one level deep to 11 real reference files (references/sources/*.md, verified present) and scripts, with explicit per-source 'cat' navigation in step 1. Content is appropriately split and easy to navigate, matching the anchor-5 example.

5 / 5

Total

18

/

20

Passed

Description

45%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 a catchy slogan that names the domain but omits concrete actions and any 'when to use' trigger guidance. It is recognizable but thin, capping completeness and limiting specificity.

Suggestions

Replace the metaphor with concrete actions, e.g. 'Resolve entities across public records and sanctions lists, build cross-linked evidence chains with explicit confidence.'

Add an explicit 'when' clause naming natural triggers: 'Use when investigating corporate due diligence, sanctions screening (OFAC/ICIJ), lobbying-to-contract patterns, or property/litigation history.'

Include key source synonyms users actually say (corporate filings, OFAC SDN, offshore leaks, due diligence) to improve trigger coverage and distinctiveness.

DimensionReasoningScore

Specificity

The phrase 'Follow the money' is a metaphor rather than a concrete action verb, and while 'public records and sanctions data' names the domain, no specific actions (resolve, cross-reference, build evidence chains) are stated. It is not a 1 because the domain is explicitly named, but it falls short of 3 since no concrete capabilities are listed.

2 / 5

Completeness

A high-level 'what' (financial investigation via public records and sanctions data) is present, but there is no 'Use when...' or equivalent 'when' guidance, which per the rubric caps completeness at 3. It is not a 2 because the 'what' is recognizable rather than entirely vague, and not a 4 because the 'when' is fully absent.

3 / 5

Trigger Term Quality

'Follow the money', 'public records', and 'sanctions data' are natural terms a user might say, but common variations and synonyms (corporate filings, OFAC, offshore leaks, due diligence, lobbying) named in the body are missing. It is not a 4 because more than a few natural terms are absent.

3 / 5

Distinctiveness Conflict Risk

'public records and sanctions data' carves a somewhat specific niche, but 'follow the money' is a broad idiom that could trigger for general investigative or campaign-finance asks, creating moderate overlap with related research skills. It is not a 4 because the description alone (without the body's 'Do NOT use' list) does not clearly fence off adjacent skills.

3 / 5

Total

11

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository
NousResearch/hermes-agent
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.