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.

71

Quality

89%

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

78%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.

A well-structured, lean instruction-only skill with a clear workflow, concrete chain template, and a properly signaled one-level-deep reference. Weakest in conciseness (recurring field lists) and actionability (no worked example), and lacks an explicit feedback loop despite implicit verification gates.

Suggestions

Dedupe the evidence-field list: define SPN, delegation mode, PAC/group data, encryption type, cache location, and accepting service once and reference it from Quick Start, Workflow, and What To Preserve instead of repeating it.

Add one worked example of a completed delegation chain (e.g. source principal -> RBCD edge -> S4U2self/S4U2proxy tickets -> target SPN -> accepting service -> resulting privilege) to make the template concrete and copy-paste ready.

Add an explicit feedback loop, e.g. 'if no service can be shown to accept the ticket, return to step 1 and re-identify the edge' so the verification gate has a defined retry path.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no padding about what Kerberos/TGTs are), but the evidence-field list (SPN, delegation mode, PAC/group data, encryption type, cache location, accepting service) recurs across Quick Start, Workflow, and What To Preserve, which could be tightened.

4 / 5

Actionability

Provides a concrete reportable chain template ('principal -> delegation edge -> ticket type -> target SPN -> accepting service -> resulting privilege') and specific fields to record, but lacks a worked example of a completed chain to anchor the guidance.

4 / 5

Workflow Clarity

A clear sequenced Quick Start plus a 3-phase workflow with verification gates ('Prove which service actually accepts the ticket', 'Separate candidate edges from the edge that really lands privilege'); this is an analysis skill so the destructive/batch validation cap does not apply, but no explicit validate-fix-retry loop is spelled out.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview with a single, clearly signaled one-level-deep reference ('Load `references/kerberos-delegation.md`...'), and that reference (verified present) appropriately splits the checklist, fields, edges, and pitfalls out of the main body.

5 / 5

Total

17

/

20

Passed

Description

95%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.

A strong, well-scoped description that explicitly answers what and when with concrete, natural trigger terms and a clear downstream-routing boundary. The only weakness is that capabilities are phrased as topic nouns rather than action verbs.

DimensionReasoningScore

Specificity

Lists several specific capabilities (S4U abuse, RBCD, constrained/unconstrained delegation, SPN trust edges, service-ticket acceptance) for the Kerberos delegation niche, but frames them as topic nouns rather than concrete action verbs, sitting just below the comprehensive verb-action anchor at 5.

4 / 5

Completeness

Explicitly states what ('CTF-sandbox workflow for Kerberos delegation, SPN trust edges, S4U abuse, RBCD...') and when ('Use when the user asks about...'), answering both with concrete trigger phrases.

5 / 5

Trigger Term Quality

'Use when the user asks about constrained delegation, unconstrained delegation, RBCD, S4U, SPNs, ticket acceptance' provides comprehensive natural trigger terms including the domain abbreviations and synonyms a CTF user would actually say.

5 / 5

Distinctiveness Conflict Risk

'Internal downstream skill for ctf-sandbox-orchestrator' plus 'Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here' carves a clear niche with an explicit routing boundary, minimizing conflict risk.

5 / 5

Total

19

/

20

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.

Validation — 16 / 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.