CtrlK
BlogDocsLog inGet started
Tessl Logo

seven-question-gate

7-question gate run before promoting a finding to FINDING + opening a report. Kills weak/non-impactful findings before they reach the report stage and damage validity ratio.

58

Quality

67%

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 ./packages/decepticon/decepticon/skills/plugins/verifier/seven-question-gate/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a lean, actionable validation checklist with a clear sequenced workflow and explicit pass/fail validation gates; its only soft spot is progressive disclosure, which is good but constrained by the absence of any bundle files.

DimensionReasoningScore

Conciseness

The body is tight: each question is a short checklist with concrete examples and no padding or re-explanation of concepts Claude already knows; only minor phrases ('This saves bounty validity-ratio...') could be trimmed.

4 / 5

Actionability

Concrete, executable guidance throughout — per-question pass/fail logic, specific PoC examples (IDOR/XSS/SQLi/SSRF), good/bad title pairs, and a copy-pasteable integration code block; minor gaps are the external cross-refs that aren't bundled.

4 / 5

Workflow Clarity

Clear sequence with explicit validation checkpoints and feedback loops: run after validate_finding but before the report, walk Q1-Q7, 'Any no → kill or re-verify', and a numbered integration section that gates update_objective on all-yes vs any-no with written reasons.

5 / 5

Progressive Disclosure

Well-organized into clear sections (questions, decision, rationale, integration, anti-patterns, cross-references); no bundle files exist so all content is inline and appropriately sectioned, though the examples/anti-patterns could conceivably be split into references if the skill grew.

4 / 5

Total

17

/

20

Passed

Description

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

The description conveys a clear purpose and niche but omits an explicit 'Use when...' trigger clause and leans on metadata for natural keywords, leaving what/when completeness and trigger-term coverage at the midpoint.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g. 'Use when validating a bug-bounty finding before submission, or when deciding whether to open a report').

Surface natural trigger synonyms from metadata.when_to_use into the description itself (e.g. 'bug bounty triage', 'validate finding', 'duplicate check').

List the gate's concrete checks (scope, impact, PoC, severity floor, reproducibility, duplicates, title) briefly so the 'what' is comprehensive rather than abstract.

DimensionReasoningScore

Specificity

Names the domain ('7-question gate', 'promoting a finding') and a couple concrete actions ('run before promoting', 'Kills weak/non-impactful findings') but is not comprehensive on what the gate actually inspects.

3 / 5

Completeness

Has a clear 'what' (a 7-question gate that kills weak findings before report) but no explicit 'Use when...' clause; the 'when' is only weakly implied, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Relevant keywords exist ('finding', 'report', 'validity ratio', 'gate') but common natural phrases users would say (e.g. 'validate finding', 'bug bounty triage') live in metadata.when_to_use rather than the description, and synonyms are missing.

3 / 5

Distinctiveness Conflict Risk

The '7-question gate' framing and validity-ratio angle carve a fairly distinct niche in bug-bounty verification, with only minor overlap risk against closely related verifier/bounty-report skills.

4 / 5

Total

13

/

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
PurpleAILAB/Decepticon
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.