CtrlK
BlogDocsLog inGet started
Tessl Logo

competition-kerberos-delegation

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for Kerberos delegation, SPN trust edges, S4U abuse, RBCD, constrained or unconstrained delegation, and service-ticket acceptance. Use when the user asks about constrained delegation, unconstrained delegation, RBCD, S4U, SPNs, ticket acceptance, or how a Kerberos trust edge turns into effective privilege under sandbox assumptions. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.

80

Quality

100%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, well-structured instruction skill: no concept padding, a concrete chain template and field checklist, a sequenced workflow with proof-gated validation, and a single real one-level reference. Token-efficient and directly actionable.

DimensionReasoningScore

Conciseness

The ~45-line body is lean and assumes Claude's competence — it never explains what Kerberos or delegation is, and every line (e.g. 'Reply in Simplified Chinese unless the user explicitly requests English') earns its place.

3 / 3

Actionability

As an instruction-only skill it gives concrete, specific guidance — a copy-ready chain template ('principal -> delegation edge -> ticket type -> target SPN -> accepting service -> resulting privilege') and an explicit field list (TGT/TGS type, PAC, encryption type, cache location) — so absent code is not penalized.

3 / 3

Workflow Clarity

A clear three-step sequence (identify edge -> trace minting/acceptance -> report effective edge) with explicit proof-validation gating ('Prove which service actually accepts the ticket', 'Reproduce one minimal delegation chain before broadening') and a checklist reference; this is analysis, not destructive/batch work, so no cap applies.

3 / 3

Progressive Disclosure

The body is a compact overview pointing to one clearly-signaled, one-level-deep reference ('Load `references/kerberos-delegation.md`...'), and that file exists on disk with the promised checklist and pitfalls — matching the clean overview anchor.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-crafted description: third-person, concrete in its capabilities, with an explicit natural-language trigger clause and clear downstream scoping that distinguishes it from sibling skills. No fluff or over-claims.

DimensionReasoningScore

Specificity

Names multiple concrete domains — 'Kerberos delegation, SPN trust edges, S4U abuse, RBCD, constrained or unconstrained delegation, and service-ticket acceptance' — rather than vague language, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what (a CTF-sandbox workflow for delegation analysis) and when (an explicit 'Use when...' trigger clause), so it is not capped at 2 by the missing-trigger guideline.

3 / 3

Trigger Term Quality

The 'Use when the user asks about constrained delegation, unconstrained delegation, RBCD, S4U, SPNs, ticket acceptance...' clause gives good coverage of natural terms a user would say, matching the top anchor.

3 / 3

Distinctiveness Conflict Risk

Scoped to a clear niche — Kerberos delegation under the sandbox — and explicitly gated as a downstream specialization 'Use only after `$ctf-sandbox-orchestrator`', making wrong-skill conflicts unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
zhaoxuya520/reverse-skill
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.