CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

autumn

Autumn billing in Epicenter: `autumn.config.ts`, `autumn-js` credit checks, `atmn` CLI, plan gates, and metered AI usage. Use when changing billing, pricing, credits, plan access, refunds, or usage events.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 highly actionable, executable integration guide with genuine domain knowledge and useful validation checkpoints. The main gaps are the absence of progressive disclosure (everything in one long file) and some redundancy between the gotchas list and earlier sections.

Suggestions

Move the CLI reference, SDK patterns, and Common Gotchas into separate reference files (e.g., references/cli.md, references/sdk.md, references/gotchas.md) and keep SKILL.md as a lean overview pointing to them one level deep.

Add one explicit end-to-end workflow section (e.g., add a plan: edit autumn.config.ts → bun x atmn preview → bun x atmn push → verify in dashboard) so the scattered checkpoints read as a single sequence.

Cut the duplicated material: Common Gotchas items 1-5 and 8 restate earlier sections, and the 'Resources' list repeats the 'Reference Repositories' links — keep one canonical location for each.

DimensionReasoningScore

Conciseness

Dense with Autumn-specific facts Claude cannot know, with no padding about general concepts; but the 'Common Gotchas' section restates points 1-5 and 8 from earlier sections, and 'Resources' duplicates the 'Reference Repositories' links.

4 / 5

Actionability

Copy-paste ready TypeScript for initialization, customer sync, checks, and refunds; complete 'atmn' CLI commands; env-key and project-file tables — fully executable and covering the common cases.

5 / 5

Workflow Clarity

Sub-workflows carry real checkpoints ('atmn preview' dry run before push, 'Validate ProductItem shapes before pushing config', blocking getOrCreate before check(), refund on error), but no single explicit end-to-end sequence such as edit config → preview → push → verify; checkpoints are scattered across topic sections.

4 / 5

Progressive Disclosure

Sections are clearly organized with headers, but there are no bundle files at all: ~350 lines inline, where the CLI reference, SDK reference, and gotchas could live in separate reference files loaded on demand.

3 / 5

Total

16

/

20

Passed

Description

87%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 description that clearly states both the concrete capabilities and explicit usage triggers for a well-scoped niche. Only minor gains available from broader synonym coverage.

DimensionReasoningScore

Specificity

Names the domain and five concrete capabilities ('autumn.config.ts', 'autumn-js credit checks', 'atmn CLI', 'plan gates', 'metered AI usage'); falls short of a 5 only because 'plan gates' is slightly generic.

4 / 5

Completeness

Explicitly answers both what (concrete named capabilities) and when ('Use when changing billing, pricing, credits, plan access, refunds, or usage events') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

'billing, pricing, credits, plan access, refunds, or usage events' gives good natural keyword coverage, but common synonyms like 'subscription', 'invoice', or 'metering' are missing.

4 / 5

Distinctiveness Conflict Risk

Names a specific niche product ('Autumn billing in Epicenter') with distinct triggers; minimal overlap risk with other skills.

5 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

EpicenterHQ/epicenter

Path

.agents/skills/autumn/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.