CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cloud-hunter-specialist-methods

Evidence-led cloud hunter technical methods and evidence interpretation for the relevant environment.

Quality

65%

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/cloud/specialist-methods/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 exemplar of token-efficient, expert-level guidance: it adds non-obvious evidentiary caveats (state provenance, credential exposure vs. validity, timeout ≠ access) without padding. Its weakness is actionability and workflow structure — it tells the reader what to scrutinize but defers all implementation to other skills and offers no sequenced procedure with checkpoints.

DimensionReasoningScore

Conciseness

The body is lean and dense with no padding and no explanation of concepts Claude already knows — e.g., 'A Terraform value may be historical, redacted, revoked or valid only in another environment; record state version and resource provenance' packs real, non-obvious guidance into every token.

5 / 5

Actionability

It names concrete tools (iam_policy_audit, tfstate_audit, k8s_audit, metadata_endpoints) and specific items to compare (explicit denies, trust policies, permission boundaries, organization controls), but implementation is deferred to other skills ('Use existing cloud/k8s technique skills') and there are no executable commands or concrete test procedures, leaving key details missing.

3 / 5

Workflow Clarity

The content is organized by domain and embeds strong verification discipline ('a timeout alone does not establish internal access', 'Correlate a request with an owned canary'), but there is no explicit step sequence or validation checkpoints — the checks are implicit rather than a sequenced workflow with feedback loops.

3 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files (references/, scripts/, assets/ are absent) and needs none; the three clearly headed sections are well organized, satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

16

/

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 identifies a clear niche (evidence-led cloud hunting) but stops at the domain level: it names no concrete actions, includes no trigger guidance for when the skill should be used, and offers few natural search terms. Adding a 'Use when...' clause with concrete capabilities and plain-language triggers would address its main gaps.

Suggestions

Add an explicit trigger clause (e.g., 'Use when conducting an authorized cloud investigation, interpreting IAM/Terraform/Kubernetes audit output, or assessing SSRF and metadata-endpoint evidence').

Replace 'technical methods' with 2-3 concrete actions such as 'interpret iam_policy_audit, tfstate_audit and k8s_audit findings' and 'validate metadata/SSRF evidence before claiming internal access'.

Include natural keywords and synonyms users would actually say (cloud investigation, cloud security, AWS, Azure, Kubernetes, SSRF, privilege escalation) to improve trigger matching and distinctiveness.

DimensionReasoningScore

Specificity

The description names the domain ('Evidence-led cloud hunter technical methods and evidence interpretation') but the actions are generic — it never states concrete operations such as auditing IAM policies or interpreting RBAC bindings, matching the 'names the domain but actions are minimal or generic' anchor rather than the 1-2 concrete actions of anchor 3.

2 / 5

Completeness

A 'what' is stated ('technical methods and evidence interpretation') but there is no 'Use when...' clause or equivalent trigger guidance — 'for the relevant environment' does not convey when to use the skill — so completeness is capped at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Some relevant keywords are present ('cloud hunter', 'evidence', 'interpretation') but common natural variations users would say (cloud investigation, cloud security, AWS/Azure/Kubernetes, SSRF) are missing, matching 'some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

'cloud hunter' and 'evidence-led' give it a somewhat specific identity, but the description could still overlap with general cloud security/technique skills and provides no distinct trigger phrases to separate it, fitting 'somewhat specific but could still overlap with similar skills' better than the 'mostly distinct' anchor.

3 / 5

Total

11

/

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/cloud/specialist-methods/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.