CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

shadowbroker

Query the ShadowBroker OSINT intelligence platform for real-time geospatial intelligence, place AI intel pins on the map, manage autonomous monitoring, inject data into native layers, fetch satellite imagery, aggregate news, generate intelligence reports, and participate in the Wormhole mesh network.

Quality

75%

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 ./openclaw-skills/shadowbroker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 exceptionally actionable — nearly every capability ships with executable code and concrete arguments — and the fast-path section is a strong navigation device. It is weakened by monolithic inlining of reference tables that belong in separate files, redundant restatement of the same rules, and no validation checkpoints around destructive/batch operations. Splitting reference material out and adding confirm-before-clear steps would lift it substantially.

Suggestions

Move the stable reference tables (Enriched Data Fields by Layer, GT analytics commands, pin categories/colors, message signature table, osint_lookup tool table) into references/ files (e.g. references/api.md, references/signatures.md) and keep SKILL.md as a concise overview with one-level-deep links.

Add explicit validation/confirmation steps before destructive and batch operations — e.g. list matching pins with get_pins() and confirm with the operator before clear_pins(), and validate batch payloads (count, categories) before place_pins_batch()/send_batch().

Deduplicate the latency tiers, anti-patterns, and 'fetch targeted, not everything' guidance that appear in both 'Agent Fast Path' and 'Important Rules', stating each rule once and cross-referencing.

DimensionReasoningScore

Conciseness

The ~780-line body is mostly dense API surface rather than general-knowledge padding, but it repeats itself: latency tiers and anti-patterns appear in both 'Agent Fast Path' and 'Important Rules', 'When to use' notes duplicate the Decision Framework, and the analysis-zone prose ('Think of them as sticky notes...') is padded. This matches anchor 3 — mostly efficient but could be tightened — rather than 4, where only minor trimming would be needed.

3 / 5

Actionability

Executable, copy-paste-ready code throughout: 'from sb_query import ShadowBrokerClient; sb = ShadowBrokerClient()', 'await sb.place_pin(lat=34.05, ..., confidence=0.8, ttl_hours=48)', 'python openclaw-skills/shadowbroker/verify_hmac.py', plus complete argument tables for osint_lookup. Specific examples cover the common cases, matching the score-5 anchor.

5 / 5

Workflow Clarity

The Decision Framework gives a clear numbered sequence with some checkpoints ('Open SSE stream first', 'geocode before pinning', 'Call sar_status() first', and the verify_hmac.py verification step), but destructive and batch operations (clear_pins(), clear_injected(), clear_analysis_zones(), place_pins_batch, send_batch) carry only 'use sparingly' advice with no validation or confirmation step. Per the rubric guideline, missing validation in destructive/batch workflows caps this dimension at 3.

3 / 5

Progressive Disclosure

No references/, scripts/, or assets/ bundle exists, so the entire tool surface is inlined in one 783-line file: the 'Enriched Data Fields by Layer' table, the GT analytics command table, the pin-category color table, and the 20-row signature table are reference material that clearly belongs in separate files. Structure (headings, a 'Fast Path (read first)' section, tables) is better than the 'minimal structure' of anchor 2, but inline reference content and the absence of any split files keep it below anchor 4.

3 / 5

Total

14

/

20

Passed

Description

75%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 highly distinctive, enumerating the platform's concrete capabilities in third person. Its main weakness is the complete absence of a 'Use when...' trigger clause, which caps completeness and leaves natural trigger phrasing underdeveloped. Adding explicit activation conditions and a few user-natural synonyms would bring it to top tier.

Suggestions

Append a trigger clause such as: 'Use when the user asks about military flights, ships, earthquakes, or conflict events, wants satellite imagery or news near a location, or asks to place intel pins on the map.'

Include natural synonyms and phrasings users would actually say (e.g. 'track flights', 'what's near me', 'intel brief') alongside the domain jargon like 'OSINT' and 'geospatial intelligence'.

State when NOT to use the skill (e.g. generic map or news questions unrelated to the ShadowBroker platform) to further reduce conflict risk.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ('place AI intel pins on the map', 'inject data into native layers', 'fetch satellite imagery', 'generate intelligence reports', 'participate in the Wormhole mesh network') with comprehensive coverage of the tool surface. It clearly matches the score-5 anchor rather than 4, which allows minor coverage gaps.

5 / 5

Completeness

The 'what' is explicit and detailed, but there is no 'Use when...' clause or equivalent trigger guidance, which the rubric explicitly caps at 3. Not 2 because the 'what' is clear rather than vague; not 4 because 'when' is entirely absent rather than weakly implied.

3 / 5

Trigger Term Quality

Concrete keywords like 'OSINT', 'geospatial intelligence', 'satellite imagery', 'news', and 'mesh network' give good coverage, but natural user phrasings (e.g. 'track flights', 'what's near me', 'map', 'intel') and synonyms/extensions are missing. This sits between anchors 3 and 4 — better than 3 because several natural nouns are present, short of 5 because no synonyms or variations are covered.

4 / 5

Distinctiveness Conflict Risk

Named proprietary surface ('ShadowBroker OSINT intelligence platform', 'Wormhole mesh network', 'AI intel pins') establishes a clear niche with minimal conflict risk against other skills. No generic phrasing would cause cross-triggering, so it matches the score-5 anchor.

5 / 5

Total

17

/

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

skill_md_line_count

SKILL.md is long (783 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

BigBodyCobain/Shadowbroker

Path

openclaw-skills/shadowbroker/SKILL.md

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.