CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

epicenter-app

Make or change an Epicenter app: its collections, actions, UI, code/data container, and private root history. Use when asked to build a personal app, change Capture, Reading, Tasks, or Vocab, set up an Epicenter, copy or share app code, or adapt code from another app on the computer that runs epicenter serve.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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.

The body is a dense, highly actionable rulebook: concrete commands, executable snippets, and real named examples cover every phase from collection design to deployment and recovery, with validation steps in the right places. Its weaknesses are structural rather than substantive — a 425-line monolith with no bundle references, and a workflow whose order must be inferred from section arrangement rather than an explicit sequence.

Suggestions

Split stable, detailed material — the UI client/Result contract and the Git recovery procedures — into files under references/ and link them from short SKILL.md sections, turning the monolith into an overview with one-level-deep references.

Add a brief ordered overview near the top (inspect an existing app → define collections → write actions → build UI → verify in a temp home → deploy only when asked) so the phase sequence is explicit rather than assembled from section headers.

Move the per-field edge-case rules (readOnly semantics, JSON Merge Patch null handling, read-tolerance of `other`/`problems`) into a collections reference file, keeping only the design decisions and one example per rule inline.

DimensionReasoningScore

Conciseness

The prose is ruthlessly compressed and project-specific ("Write last.", "Annotate honestly.", "Never keep two writable copies in step") with no explanation of concepts Claude already knows, fitting anchor 4's 'efficient; minor instances that could be trimmed'. It is not a 5 because the 25 KB monolithic body includes sections (UI client contract details, recovery minutiae) whose volume could be reduced by offloading to reference files.

4 / 5

Actionability

Guidance is fully executable throughout: a copy-paste-ready temp-home verification shell block, complete TypeScript snippets (`await words.update({ path }, (word) => ({ reps: (word?.reps ?? 0) + 1 }))`, `connect<typeof tasksApp>()`), exact commands (`epicenter new --from`, `git restore --source=<commit> -- apps/<app>/data/`), and named real examples (Tasks' `add`, Vocab's `review`) covering the common cases. This matches anchor 5 rather than 4, whose 'minor gaps' are not evident.

5 / 5

Workflow Clarity

Clear phased structure (decide files → actions → UI → verify → server → recovery) with genuine validation points ("run `epicenter build <app>` to check it before opening its page", "Read each record's `other` and `problems` afterward", the failed-build feedback loop), matching anchor 4. It falls short of anchor 5 because the end-to-end sequence is never laid out as an ordered path — the reader must assemble the order from section headers and scattered rules, and some checkpoints (e.g., typecheck placement) are implicit.

4 / 5

Progressive Disclosure

The bundle contains no reference, script, or asset files at all; everything, including the full UI client contract and Git recovery procedures, is inlined in a ~425-line SKILL.md. Section headers are well organized and external pointers are clearly named (`packages/app/README.md`, `../product-collapse/SKILL.md`, `query-layer`), which keeps it above anchor 2, but content that clearly belongs in separate reference files is inline — the anchor-3 pattern.

3 / 5

Total

16

/

20

Passed

Description

100%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 exemplary: it states concrete capabilities in third-person imperative form, enumerates the app's components, and pairs a clear 'what' with an explicit 'Use when' clause full of natural trigger phrases naming the ecosystem's apps and operations. Every dimension lands on the top anchor with no fluff, over-claims, or padding.

DimensionReasoningScore

Specificity

The description names the app's concrete components ("collections, actions, UI, code/data container, and private root history") and lists multiple specific operations: build a personal app, change Capture/Reading/Tasks/Vocab, set up an Epicenter, copy or share app code, and adapt code from another app. This matches the anchor-5 example's breadth of concrete actions with no vague filler to place it at 4.

5 / 5

Completeness

It explicitly answers both questions: the first sentence states what the skill does, and "Use when asked to build a personal app, change Capture, Reading, Tasks, or Vocab, set up an Epicenter, copy or share app code, or adapt code from another app..." gives concrete trigger phrases. This mirrors the anchor-5 exemplar exactly; anchor 4's weaker 'when' does not apply.

5 / 5

Trigger Term Quality

It uses the natural phrases a user of this ecosystem would say — "build a personal app", "change Capture, Reading, Tasks, or Vocab", "set up an Epicenter", "copy or share app code", "epicenter serve" — covering the domain's full working vocabulary rather than a few generic keywords. Anchor 4's 'a few natural terms missing' does not fit; no domain synonym or extension is conspicuously absent.

5 / 5

Distinctiveness Conflict Risk

"Epicenter" and the named apps (Capture, Reading, Tasks, Vocab) establish a clear niche with distinct triggers, so overlap with other skills is minimal. It is the opposite of the generic anchors at 1-3, and no closely related skill shares these triggers to justify 4.

5 / 5

Total

20

/

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: 2 suspicious

Warning

Total

15

/

16

Passed

Repository

EpicenterHQ/epicenter

Path

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