CtrlK
BlogDocsLog inGet started
Tessl Logo

sentry-security

Sentry-specific security review based on real vulnerability history. Use when reviewing Sentry endpoints, serializers, or views for security issues. Trigger keywords: "sentry security review", "check for IDOR", "access control review", "org scoping", "cross-org", "security audit endpoint".

76

Quality

93%

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

92%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, highly actionable security-review skill with concrete code patterns, a clear sequenced workflow with confidence-based validation checkpoints, and clean one-level-deep reference files. The only slight weakness is minor verbosity in the explanatory framing.

Suggestions

Tighten the repeated "X patches last year" framing into a single prioritization note so the per-check headers stay lean.

Replace a few explanatory sentences in Step 3 with bulletized checks to further reduce token overhead while preserving the enforcement-chain logic.

DimensionReasoningScore

Conciseness

Dense, Sentry-specific guidance that assumes Claude's competence (no generic OWASP theory, concrete red/safe patterns); a few explanatory passages and repeated "X patches last year" framing could be trimmed, keeping it just below a 5.

4 / 5

Actionability

Concrete grep-able code patterns (e.g. `Model.objects.get(id=request.data[...])`), explicit trace flows, a copy-paste-ready report template, and specific safe patterns make the guidance fully executable.

5 / 5

Workflow Clarity

A clear 4-step sequence (Classify → Check classes → Trace enforcement chain → Report) with explicit validation checkpoints: the HIGH/MEDIUM/LOW confidence table, "mark MEDIUM not HIGH," and "stop and report zero findings" provide feedback loops for confidence calibration.

5 / 5

Progressive Disclosure

SKILL.md is an overview with well-signaled, one-level-deep references mapped via a code-type table (endpoint-patterns.md, serializer-patterns.md, etc.), all of which are real files in ./references/; content is appropriately split with easy navigation.

5 / 5

Total

19

/

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-targeted description that clearly states purpose and trigger conditions with natural keywords and minimal conflict risk. The only minor weakness is that the action list is somewhat single-verb (reviewing) rather than enumerating distinct concrete actions.

DimensionReasoningScore

Specificity

Names the domain and several concrete review targets ("reviewing Sentry endpoints, serializers, or views for security issues") with only minor coverage gaps; not a maximal 5 because it relies on one verb (reviewing) rather than enumerating multiple distinct actions.

4 / 5

Completeness

Explicitly answers both what ("Sentry-specific security review based on real vulnerability history") and when ("Use when reviewing Sentry endpoints, serializers, or views") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger keywords including synonyms and abbreviations ("sentry security review", "check for IDOR", "access control review", "org scoping", "cross-org", "security audit endpoint") that a user would naturally say.

5 / 5

Distinctiveness Conflict Risk

A clearly niche, Sentry-specific scope with distinct triggers makes conflict with other skills minimal; the language is third-person and tightly scoped.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
getsentry/sentry
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.