CtrlK
BlogDocsLog inGet started
Tessl Logo

auditor

Auditor independiente. Toma T-{n}-result.md + corre tests él mismo (NO se fía del dev). Spawna agents auditor-{be,fe,agentic} según surface del ticket. Veredicto: APPROVED | CHANGES_REQUESTED | ESCALATED. Self-fix triviales (lint/typo/format) cap 2 iter. Diseño/security/arch → escala. Cuando todos tickets del story audit-passed, escribe REVIEW-final.md. Activa cuando user dice: '/auditor', 'auditá T-N', 'revisá ticket', 'verdict'.

72

Quality

90%

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

88%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 workflow with explicit validation, feedback loops, and escalation paths. Its main weaknesses are minor redundancy in the self-fix policy and the absence of any progressive-disclosure split into reference files.

Suggestions

Consolidate the self-fix policy so it lives in one place (either the Step 3 Case C block or the detailed table) instead of being described twice.

Extract the per-surface sub-auditor category lists (BE 11 / FE 12 / AGENTIC 14 categories) into reference files the sub-auditors load, reducing SKILL.md length and enabling progressive disclosure.

DimensionReasoningScore

Conciseness

Dense and terse with tables and code blocks, assuming Claude knows DDD/FSD/LangGraph without explaining them; the self-fix policy is stated both inline in Step 3 Case C and again in the detailed table, a minor redundancy that could be consolidated.

4 / 5

Actionability

Provides executable bash (git log/diff, ruff format/check, git commit/push), concrete Agent() spawn templates with prompt bodies, and exact YAML state-transition snippets covering the common cases.

5 / 5

Workflow Clarity

Clear Steps 1-5 with explicit validation ('Re-correr quality gates; Si verde → APPROVED; Si falla → CHANGES_REQUESTED'), feedback loops (audit→fix→re-audit with cap 2 then escalate), and anti-pattern/self-fix checklists for the destructive git-push operations.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections with no monolithic wall of text and no problematic inlining of reference material, though it is a single file with no bundle references to split content one level deeper.

4 / 5

Total

18

/

20

Passed

Description

92%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, concrete description that names specific actions, surfaces, verdicts, and explicit activation triggers. It is highly specific and distinctive with a clear when-clause; only trigger-term synonym coverage has minor room to grow.

Suggestions

Add a few synonym trigger phrases (e.g. 'revisá el ticket T-N', 'auditá story', 'code review') to broaden natural-term coverage.

Consider naming the concrete quality-gate commands the auditor runs so the description previews the verification it performs.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Toma T-{n}-result.md + corre tests él mismo', 'Spawna agents auditor-{be,fe,agentic}', 'Veredicto: APPROVED | CHANGES_REQUESTED | ESCALATED', 'Self-fix triviales ... cap 2 iter', 'escribe REVIEW-final.md' — giving comprehensive coverage.

5 / 5

Completeness

Clearly answers 'what' (independent auditor that runs tests, spawns sub-auditors, emits verdicts, self-fixes, writes final review) and explicitly answers 'when' with a concrete 'Activa cuando user dice' trigger clause.

5 / 5

Trigger Term Quality

Provides explicit natural triggers ('Activa cuando user dice: /auditor, auditá T-N, revisá ticket, verdict') with good keyword coverage, but offers few synonyms beyond these four phrases.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (independent code auditor with verdicts and sub-auditors per surface) and uses distinct command-style triggers, giving minimal overlap with other skills.

5 / 5

Total

19

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
alpacapurpura/ap_sales_agent
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.