CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

security-ownership-map

Analyze git-history security ownership when sensitive files, CODEOWNERS coverage, bus factor, contributor concentration, and remediation evidence need mapping.

Quality

77%

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 ./Skills/security-ops/security-ownership-map/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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, safety-conscious skill body with clear sections, good failure handling, and real verified bundle references. Its weaknesses are the absence of any executable git commands or in-bundle scripts (the referenced archived scripts live elsewhere) and redundant repetition of the redaction rules across four sections.

Suggestions

Add one or two concrete executable commands to the Workflow section (e.g. a git log attribution command with author/committer formatting) so the analysis steps can be run without improvising the tooling.

Consolidate the redaction/safety rules repeated across Avoid, Constraints, Execution Boundaries, and Workflow into a single authoritative section to remove redundancy.

Move the out-of-bundle 'Infrastructure/references/...' pointers into the single Progressive Disclosure entry for the deferred-context directory, or replace them with paths that are resolvable from this skill's bundle.

DimensionReasoningScore

Conciseness

The body is a lean bullet-based skill with no concept explanations and no padding — every section (When To Use, Inputs, Outputs, Workflow, Failure Mode) earns its place. It stops short of anchor 5 because the same safety instruction is repeated across four sections ('Raw secret, private email, or sensitive commit content in chat' in Avoid, 'Redact secrets and sensitive data by default' in Constraints, 'Do not publish raw private emails...' in Execution Boundaries, and 'Redact sensitive details' in Workflow), which could be consolidated.

4 / 5

Actionability

The guidance is specific about process (confirm scope and attribution model, compare observed maintainers with CODEOWNERS, start with 2-3 focused surfaces) but contains no executable detail: no git commands (e.g. a `git log --format` attribution command), no script invocations, and the referenced 'archived ownership-map scripts' are not in this bundle. For an instruction-only skill this fits anchor 3 ('some concrete guidance but incomplete') — more than high-level hints, but missing the key execution details.

3 / 5

Workflow Clarity

The Workflow section gives a coherent ordered sequence (scope confirmation, evidence gathering, comparison, redaction, recommendations) and the Failure Mode section supplies error-recovery checkpoints ('classify whether the blocker is repository state, permissions, tooling, or ambiguous scope', 'return a blocked result with the exact filesystem error'). It misses anchor 5 because the Validation section targets changes to the skill itself rather than validating the analysis output, so the operational workflow lacks an inline output-verification checkpoint.

4 / 5

Progressive Disclosure

The Progressive Disclosure section clearly signals one-level-deep references that exist in the bundle (references/contract.yaml, references/evals.yaml, references/task-profile.json — all verified present) alongside a See Also cross-link table. It misses anchor 5 because four references point to 'Infrastructure/references/...' paths outside this bundle, which are unverifiable from the skill itself and blur the navigation surface.

4 / 5

Total

15

/

20

Passed

Description

78%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 description: concrete domain, explicit when-clause, and distinctive niche terms like CODEOWNERS and bus factor. Main gap is that one verb covers all actions and the when-clause describes the data needing mapping rather than the user situations that should trigger the skill.

DimensionReasoningScore

Specificity

The description names the domain ('Analyze git-history security ownership') and enumerates five concrete analysis targets: 'sensitive files, CODEOWNERS coverage, bus factor, contributor concentration, and remediation evidence'. This matches the anchor 'lists several specific actions; minor gaps in coverage' — it stays above anchor 3 because the target list is broad and concrete, but below anchor 5 because a single verb ('analyze... mapping') carries all the actions, unlike the multi-verb comprehensiveness of the anchor-5 example.

4 / 5

Completeness

Both 'what' ('Analyze git-history security ownership... need mapping') and 'when' (the explicit 'when sensitive files, CODEOWNERS coverage, bus factor... need mapping' clause) are present, so it is not capped at 3. It sits at anchor 4 rather than 5 because the 'when' clause is phrased as the analysis targets needing mapping rather than concrete user situations or requests ('Use when the user asks who owns...'), making it less explicit than the anchor-5 pattern.

4 / 5

Trigger Term Quality

It includes natural terms users would say: 'CODEOWNERS', 'bus factor', 'sensitive files', 'git-history', 'remediation'. This fits anchor 4 ('good keyword coverage; a few natural terms missing') — common user phrasings like 'who maintains', 'single point of failure', or 'blame' are absent, so it falls short of anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The combination of 'git-history security ownership', 'CODEOWNERS coverage', and 'bus factor' carves out a clear niche with distinct trigger terms unlikely to fire for unrelated git or security skills. This matches anchor 5 ('clear niche with distinct triggers; minimal conflict risk'); anchor 4's 'minor overlap risk with closely related skills' would understate how distinctive the CODEOWNERS/bus-factor pairing is.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Skills/security-ops/security-ownership-map/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.