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.

61

Quality

72%

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

85%Weight 40%Scale 1-3

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 with explicit validation checkpoints and a clear pass/kill decision flow. Its only weakness is mild verbosity in the motivational sections that could be trimmed without losing clarity.

Suggestions

Tighten the 'Why this gate matters' section — the 90% vs 30% validity-ratio narrative is motivational padding; a one-line rationale would suffice.

Trim restated context within each question (e.g. 'The validate_finding result is necessary but not sufficient') to keep the decision criteria scannable.

Consider moving the worked integration pseudocode into a references file if the skill grows, keeping SKILL.md as the gate logic overview.

DimensionReasoningScore

Conciseness

The body is mostly efficient and action-oriented, but sections like 'Why this gate matters' and the prose around each question add explanatory padding (e.g. validity-ratio earnings narrative) that could be tightened without losing the actionable core.

2 / 3

Actionability

Each question gives concrete decision criteria with copy-paste-ready examples — exact impact statements, good/bad title pairs, and a runnable Integration code block with real kg_add_node/update_objective calls.

3 / 3

Workflow Clarity

A clear 7-step sequence with an explicit decision checkpoint ('If all 7 are yes proceed; if any is no kill'), plus the Integration section encodes a validate -> gate -> pass/blocked feedback loop with recorded reasons.

3 / 3

Progressive Disclosure

A self-contained, well-organized single-purpose skill with clear section headers (questions, Decision, Anti-patterns, Cross-references) and one-level cross-references; no bundle files exist so the body appropriately holds all content inline.

3 / 3

Total

11

/

12

Passed

Description

60%Weight 40%Scale 1-3

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 concrete, distinctive purpose but reads as one dense run-on sentence with no explicit 'Use when' trigger guidance. It describes the what well but leaves the when mostly implied.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g. 'Use after validate_finding succeeds and before drafting a report, to decide whether a finding is worth submitting').

Surface natural trigger terms users would say — 'triage', 'should I report this finding', 'validity ratio', 'bug bounty submit' — instead of burying them in one long sentence.

Split the run-on sentence so the gate's purpose ('kills weak findings before they reach the report stage') stands alone and is scannable.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "run before promoting a finding", "Kills weak/non-impactful findings", "opening a report" — tied to a specific gate mechanism rather than vague language.

3 / 3

Completeness

Clearly states what the skill does, but the "when" is only implied via "run before promoting a finding" — there is no explicit "Use when..." trigger clause, which caps completeness at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

Includes some natural terms a user would say ("validate finding", "report", "duplicate") but they are embedded in a single long clause and miss common variations like "triage", "bug bounty", or "should I submit".

2 / 3

Distinctiveness Conflict Risk

The niche (a pre-report triage gate) is fairly specific, but "validate finding before report" could still overlap with general verifier or bounty-report skills without a sharper distinguishing trigger.

2 / 3

Total

9

/

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

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.