CtrlK
BlogDocsLog inGet started
Tessl Logo

sast-missingauth

Detect missing authentication and broken function-level authorization vulnerabilities in a codebase using a three-phase approach: recon (map endpoints and the role/permission system), batched verify (check auth/authz in parallel subagents, 3 endpoints each), and merge (consolidate batch results). Covers unauthenticated access and vertical privilege escalation (e.g., regular user accessing admin-only functions). Requires sast/architecture.md (run sast-analysis first). Outputs findings to sast/missingauth-results.md. Use when asked to find missing auth, broken access control, or privilege escalation bugs.

68

Quality

82%

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

65%

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

The body is highly actionable and well-structured for a multi-framework security assessment, but it is long and monolithic, with redundant example sections and no bundle-file separation. Workflow sequencing is strong but lacks a verification checkpoint on batch results.

Suggestions

Add an explicit validation/verification step before Phase 3 (e.g., check that every recon endpoint appears in a batch file and that classifications are consistent) so the batched operation has a feedback checkpoint.

Split the eight framework 'Vulnerable vs. Secure Examples' into one-level-deep reference files (e.g., references/examples-django.md) and have Phase 2 load only the matching stack, reducing inline bulk and improving progressive disclosure.

Merge the overlapping 'Authorization Patterns That PREVENT Vulnerabilities' and 'Vulnerable vs. Secure Examples' sections into one set per framework to remove redundancy and tighten conciseness.

DimensionReasoningScore

Conciseness

Largely instructive rather than padded with concepts Claude knows, but the 'Authorization Patterns That PREVENT Vulnerabilities' and 'Vulnerable vs. Secure Examples' sections overlap heavily across the same 8 frameworks, so it could be tightened.

2 / 3

Actionability

Provides copy-paste-ready subagent prompts, concrete per-framework code in VULNERABLE/SECURE pairs, exact output templates, and explicit classification rules — fully executable guidance.

3 / 3

Workflow Clarity

Three phases are clearly sequenced with explicit ordering dependencies and batch sizing, but the batched verify operation has no validation/verification checkpoint on batch outputs before merge, capping clarity at 2 per the batch-operations guideline.

2 / 3

Progressive Disclosure

Well-organized with clear headers, but it is a monolithic ~580-line file with no reference files — the 8 framework example sets are content that should be split into one-level-deep references rather than inlined.

2 / 3

Total

9

/

12

Passed

Description

100%

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 is third-person, specific, and fully covers both capability and trigger conditions with natural terms. It is distinguishable from adjacent SAST skills and avoids vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Detect missing authentication and broken function-level authorization vulnerabilities', plus the three-phase 'recon', 'batched verify (check auth/authz in parallel subagents, 3 endpoints each)', and 'merge (consolidate batch results)'.

3 / 3

Completeness

Explicitly answers both what (detect the vulnerabilities via a three-phase approach) and when via the 'Use when asked to find missing auth, broken access control, or privilege escalation bugs' clause.

3 / 3

Trigger Term Quality

Includes natural user-facing terms 'missing auth, broken access control, or privilege escalation bugs' plus 'unauthenticated access and vertical privilege escalation', covering common phrasings a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Clear niche (vertical escalation + unauthenticated access) with explicit triggers and scoping against IDOR/horizontal escalation and sast-jwt, making it unlikely to fire for the wrong skill.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (580 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
utkusen/sast-skills
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.