CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

chatto-jobs-implementation

Add, change, or remove a Chatto background job type, or change the policy, handler, or payload of one. Use before you enqueue new work on the JOBS queue in cli/internal/core, and when a job type shows as Unknown on the Jobs page.

Quality

96%

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

100%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 exemplary: dense, non-obvious domain rules; an actionable sequenced checklist with exact paths and symbols; explicit verification commands; and disciplined conditional pointers to deeper documentation. It neither pads nor omits, and reads as a model project-specific skill.

DimensionReasoningScore

Conciseness

Every line carries project-specific policy Claude could not know (names persisted in job facts and JOBS subjects, payload opacity rules, `*jobs.Failure` categories, `jobs.UnlimitedAttempts` semantics) with no padding and no explanation of known concepts. It matches the 5 anchor "lean and efficient; every token earns its place" — there is nothing to trim without losing real guidance.

5 / 5

Actionability

Guidance is fully executable: exact symbols (`jobTypes()` in `cli/internal/core/jobs.go`, `knownJobTypeLabel` in a full frontend path, `runJobs`), exact file targets (`testdata/jobs/types.json`, `jobs.proto`, message catalogs), and copy-paste commands (`mise x -- go test ...`, `mise codegen-proto`, `mise license-check`). This matches the 5 anchor; nothing remains pseudocode or high-level.

5 / 5

Workflow Clarity

The 8-step numbered checklist is clearly sequenced with per-step file targets, capped by a Verification section of exact runnable commands ("Run the checks below"). This matches the 5 anchor's "clear sequence with explicit validation steps ... checklists for complex processes"; the validation the destructive/batch cap tests for is present, so no cap applies.

5 / 5

Progressive Disclosure

The single SKILL.md is a well-organized overview, and all deeper material is one level deep with conditional loading guidance ("Read ADR-123 and FDR-056 first", "Read pkg/jobs/AGENTS.md only when you change the shared module", pointers to a sibling architecture-inventory skill). This matches the 5 anchor's clear overview with well-signaled references and easy navigation; no bundle files exist to inline incorrectly.

5 / 5

Total

20

/

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.

The description is a strong exemplar: it states concrete capabilities in third person, gives an explicit "Use when" clause with two concrete trigger conditions, and is tightly scoped to a distinct niche. The only minor gap is that a few natural synonym phrasings are not covered.

DimensionReasoningScore

Specificity

"Add, change, or remove a Chatto background job type, or change the policy, handler, or payload of one" lists multiple specific concrete actions (add/change/remove job type, change policy, handler, payload) with comprehensive coverage of the skill's domain. It exceeds the 4 anchor because there are no minor gaps in coverage of the job-type lifecycle.

5 / 5

Completeness

It explicitly answers both "what" (add, change, or remove a job type, or change its policy, handler, or payload) and "when" ("Use before you enqueue new work on the JOBS queue in cli/internal/core, and when a job type shows as Unknown on the Jobs page") with concrete trigger phrases. This matches the 5 anchor exactly; the 4 anchor's caveat about a less-explicit 'when' does not apply.

5 / 5

Trigger Term Quality

Natural trigger phrases are present — "background job type", "enqueue new work on the JOBS queue", "job type shows as Unknown on the Jobs page" — phrasing a user would naturally say. It falls short of the 5 anchor because a few natural synonyms and variations (e.g., "worker", "scheduled task", "retry a job") are missing.

4 / 5

Distinctiveness Conflict Risk

Distinctive niche triggers — "Chatto background job type", "JOBS queue", "cli/internal/core", "the Jobs page" — make confusion with other skills very unlikely. It clearly matches the 5 anchor's "clear niche with distinct triggers; minimal conflict risk" rather than the 4 anchor, which requires some overlap risk with closely related 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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 9 suspicious

Warning

Total

15

/

16

Passed

Repository

chattocorp/chatto

Path

.agents/skills/chatto-jobs-implementation/SKILL.md

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.