CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ad-operator-specialist-methods

Evidence-led ad operator technical methods and evidence interpretation for the relevant environment.

Quality

55%

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

Quality

Content

62%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 guidance: zero padding, full assumption of competence, and genuinely non-obvious evidentiary distinctions (potential vs. proven rights, replication-rights vs. DA membership, state changes vs. read-only checks). Its weaknesses are the mirror image: no executable steps or sequenced workflow, and deferral to unnamed technique skills leaves the reader without a path to implementation details.

Suggestions

Name the sibling technique skills (or their invocation paths) when deferring implementation details, so "Use the relevant existing technique skills" becomes a navigable reference.

Add a short sequenced evidence-handling checklist (collect → confirm vs. potential via kg_record → record encryption type/account policy → capture before/after state for authorized validations) with explicit validation checkpoints, which would also lift workflow clarity.

Include one or two concrete command or schema examples for the named tools (bh_ingest_zip, kg_record) so the pivotal collect-vs-confirm distinction is directly executable.

DimensionReasoningScore

Conciseness

The body is dense expert guidance that assumes competence — it name-drops DCSync, ESC templates, RBCD, ReadGMSAPassword without explaining any of them, and every sentence carries a non-obvious evidentiary distinction. Nothing can be trimmed without losing information.

5 / 5

Actionability

Concrete hooks exist (`bh_ingest_zip`, `kg_record`, GetChanges/GetChangesAll, ReadLAPSPassword/ReadGMSAPassword distinctions), but execution is deferred to unnamed "relevant existing technique skills" and "existing ADCS and Kerberos technique skills" with no names or paths — key details for acting on the guidance are missing.

3 / 5

Workflow Clarity

No sequence of steps exists anywhere in the body — it is a collection of interpretive cautions, and even the state-change validation discussion ("Capture the effective principal, object, permission source and before/after state") is a requirement statement, not a checkpoint-embedded workflow. It sits between the steps-missing anchor 1 (mitigated by present validation awareness) and the rough-sequence anchor 2 (no sequence present).

2 / 5

Progressive Disclosure

At ~30 lines with two well-organized thematic sections and no bundle files to manage, structure is appropriate, but the references to sibling technique skills are not well-signaled — they are invoked generically ("the relevant existing technique skills") without names or paths, a minor navigation gap that keeps it below the 5 anchor.

4 / 5

Total

14

/

20

Passed

Description

28%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 domain but communicates almost nothing actionable: no concrete capabilities, no natural trigger terms, and no use-when guidance, with filler like "for the relevant environment" diluting what little specificity exists. It would rarely win a trigger competition against better-described sibling skills.

Suggestions

Add an explicit trigger clause, e.g. "Use when investigating Active Directory attack paths, reviewing BloodHound/ADCS findings, or interpreting DCSync, delegation, or LAPS/GMSA evidence."

Replace generic phrasing with concrete actions and natural keywords users would actually say: Active Directory, AD, BloodHound, Kerberos, ADCS, DCSync, delegation, attack paths.

Drop the filler "for the relevant environment" and state what the skill concretely provides (e.g., evidentiary limits, topology vs. confirmed-rights distinctions, state-change validation requirements).

DimensionReasoningScore

Specificity

The description names its domain ("ad operator technical methods and evidence interpretation") but offers no concrete actions — "technical methods" and "evidence interpretation" are generic noun phrases, not the specific verbs a 3+ anchor requires.

2 / 5

Completeness

The "what" is vague ("technical methods and evidence interpretation") and the "when" is entirely absent — "for the relevant environment" is not a trigger clause, so the missing-'Use when' cap applies and the vague-what/no-when anchor fits best.

2 / 5

Trigger Term Quality

Only "ad operator" and "evidence" function as keywords, and "ad operator" is upstream jargon rather than a phrase users naturally say; the natural terms users would utter (Active Directory, AD, BloodHound, Kerberos, DCSync, attack path) are absent.

2 / 5

Distinctiveness Conflict Risk

The "ad operator" niche gives it some specificity, but "Evidence-led ... for the relevant environment" is generic filler that could overlap with other security-investigation or evidence-handling skills.

3 / 5

Total

9

/

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/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.