CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bloodhound-bhce

BloodHound CE runtime selection and collection analysis for hosted MCP or standalone OSS tools.

Quality

74%

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 ./packages/decepticon/decepticon/skills/standard/ad/bloodhound-bhce/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 an excellent example of a lean instruction-only skill: it gives concrete tool-level guidance for both runtime branches, includes an explicit ingest verification checkpoint, and avoids all padding. The only gaps are minor — no invocation examples for the named tools and no error-recovery guidance if ingestion or data quality fails.

DimensionReasoningScore

Conciseness

The body is ~180 words covering a branching tool-selection scenario with zero padding: it never explains what BloodHound, Active Directory, or attack paths are, and every clause maps to a concrete tool name, constraint ('Never mix their data or credentials'), or deprecation note ('The retired in-house bh_ingest_zip and related wrappers are deprecated'). This matches 'lean and efficient; assumes Claude's competence; every token earns its place'.

5 / 5

Actionability

The body names eleven concrete tools (bloodhound_mcp_upload_collection, bloodhound_mcp_data_quality, bhce_status, bhce_ingest_zip, etc.) with preconditions and constraints ('ingests an authorized ZIP under /workspace', 'only for bounded read-only questions'), matching 'mostly executable guidance; concrete code or commands with minor gaps'. It falls short of fully executable because no invocation examples are given (e.g., a sample bounded Cypher query or argument shapes for find_objects).

4 / 5

Workflow Clarity

The sequence is clear for both branches: identify available tools, then hosted (upload, verify terminal 'Complete', run analysis tools) or standalone (bhce_status, bhce_ingest_zip, bhce_cypher). Validation for the batch ingest operation is present ('Verify terminal Complete' plus bloodhound_mcp_data_quality as a post-ingest checkpoint), so the batch-operation cap does not apply; however there is no error-recovery feedback loop for a failed upload or poor data quality, matching 'clear sequence with most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

The body is under 50 lines with no bundle files to reference, and its paragraph structure (runtime selection, hosted path, standalone path) is well organized, matching the rubric's simple-skill guidance. The one external reference (/skills/standard/ad/bloodhound-query/SKILL.md) is clearly signaled and one level deep ('Load ... only when its detailed procedure is relevant'), matching the well-signaled one-level-deep reference anchor.

5 / 5

Total

18

/

20

Passed

Description

53%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 identifies a clear niche (BloodHound CE) and a high-level purpose, but it reads more like an internal routing note than a trigger-optimized skill description. It lacks an explicit 'Use when...' clause and the natural trigger terms (SharpHound, attack paths, ingest) that would let a user's request reliably surface this skill.

Suggestions

Add an explicit 'Use when...' clause with natural triggers, e.g. 'Use when the user mentions BloodHound, BloodHound CE, SharpHound, collection ZIPs, ingest, or AD attack paths'.

Enumerate the concrete actions the skill performs (ingest a collection ZIP, check data quality, explore domain overview, find exposure and shortest attack paths) instead of the abstract phrase 'collection analysis'.

Include common synonyms users actually say (SharpHound, BHCE, attack paths) in the description itself rather than only in the when_to_use metadata field.

DimensionReasoningScore

Specificity

The description names the domain ('BloodHound CE') and two actions ('runtime selection and collection analysis'), matching the anchor for naming a domain plus 1-2 concrete actions. It does not enumerate the skill's several concrete capabilities (ZIP ingest, data quality checks, attack-path finding), so it falls short of the 'several specific actions' anchor.

3 / 5

Completeness

The 'what' is stated ('runtime selection and collection analysis for hosted MCP or standalone OSS tools') but there is no 'Use when...' clause or equivalent explicit trigger guidance in the description, capping completeness at 3 per the rubric guideline. The frontmatter's separate when_to_use metadata field is not part of the description being evaluated.

3 / 5

Trigger Term Quality

'BloodHound CE' and 'collection' are natural terms a user would say, but common variations and synonyms such as 'SharpHound', 'bhce', 'attack paths', and 'ingest' are absent from the description, matching 'some relevant keywords but missing common variations or synonyms'. Phrases like 'runtime selection' and 'standalone OSS' are internal jargon rather than user-natural triggers.

3 / 5

Distinctiveness Conflict Risk

'BloodHound CE' pins a clear niche with low conflict risk against unrelated skills, but the 'collection analysis' portion overlaps with a closely related bloodhound-query skill (referenced in the body), matching 'mostly distinct; minor overlap risk with closely related skills'. It is far more specific than the 'somewhat specific' anchor, which uses generic domain language.

4 / 5

Total

13

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/standard/ad/bloodhound-bhce/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.