CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

auth

Epicenter account package: `@epicenter/account`, the auth client Svelte reads through `reactive`, OAuth sign-in for browser and desktop apps, the Account lifetime, account-bound fetch, and hosted resource authorization. Use when editing Epicenter auth clients, session state, hosted sign-in, or how a route boots from auth.

Quality

89%

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

90%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.

An exemplary instruction-only skill body: token-dense, purely project-specific, and actionable at the symbol level, with embedded verification checkpoints in its mini-workflows. The only meaningful improvement areas are pulling inline session-policy detail into a reference and adding a feedback-loop pattern for error recovery.

DimensionReasoningScore

Conciseness

The ~80-line body is dense, purely project-specific constraint ("An Account refuses foreign origins before attaching credentials and does not follow redirects"), explains nothing Claude already knows, and explicitly economizes ("Do not restate either here or in code comments"). This matches the 5 anchor — lean, assumes competence, every token earns its place — and is clearly not the 4 anchor, which requires identifiable over-explanation to trim.

5 / 5

Actionability

Guidance is concrete throughout: exact constructors per app type in the composition table (`createBrowserOAuth`, `createTauriAuth()`, `createCookieSessionAuth`), exact options ("`account.fetch` uses `credentials: 'omit'`"), exact verbs (`startSignIn`/`completeSignIn`), exact keying (`{#key auth.state.account}`), and explicit status mapping (401 vs retryable 503). Per the rubric's instruction-only note, absent code is not penalized when guidance is this actionable; specific examples cover the common cases, matching 5 rather than 4's "minor gaps".

5 / 5

Workflow Clarity

Several mini-workflows carry real checkpoints: "ask DeepWiki a narrow question…, then verify decisive details against the installed source", "Pending work checks the captured Account after each await", and "Test provider-link callback binding and implicit same-email linking separately". This matches 4's "clear sequence with most checkpoints present"; it is not 5 because no end-to-end validate→fix→retry feedback loop is laid out, and not 3 because checkpoints are explicit rather than missing.

4 / 5

Progressive Disclosure

Sections are well-labeled and delegation is exemplary and one level deep ("The README owns the explanation; the contract owns the signatures"), matching the 4 anchor's good structure with minor gaps. It falls short of 5 because there is no quick-start/navigation framing and fairly deep operational detail is inlined (session-policy specifics: 30-day sliding expiry, `freshAge` 600 seconds) that a stricter split would move to a reference file.

4 / 5

Total

18

/

20

Passed

Description

83%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, project-scoped description that names concrete capabilities and includes an explicit, specific 'Use when…' trigger clause. Its main limitation is keyword synonym coverage (no 'login'/'authentication' variants) and trigger words broad enough to risk minor overlap with sibling Epicenter skills.

DimensionReasoningScore

Specificity

The description enumerates several concrete items — "OAuth sign-in for browser and desktop apps", "account-bound fetch", "hosted resource authorization", "the Account lifetime" — giving minor gaps in coverage rather than the comprehensive, action-verb list of the 5 anchor. It exceeds the 3 anchor's "1-2 concrete actions" since five-plus specific capabilities are named.

4 / 5

Completeness

It explicitly answers both: the "what" is the enumerated package scope ("the auth client Svelte reads through `reactive`, OAuth sign-in…, account-bound fetch, and hosted resource authorization"), and the "when" is the explicit clause "Use when editing Epicenter auth clients, session state, hosted sign-in, or how a route boots from auth" with concrete trigger conditions. This matches the 5 anchor; it is not 4 because the 'when' is already explicit and specific.

5 / 5

Trigger Term Quality

Natural terms a user would say are present — "auth clients", "sign-in", "session state", "account", "OAuth" — matching the 4 anchor's "good keyword coverage; a few natural terms missing". It falls short of 5 because common synonyms like "login", "log in", and "authentication" are absent.

4 / 5

Distinctiveness Conflict Risk

"Epicenter account package" and `@epicenter/account` carve a clear niche, but broadly worded triggers such as "session state" and "how a route boots from auth" could overlap with closely related skills (e.g., server session-policy or Svelte reactive skills). This matches the 4 anchor's "mostly distinct; minor overlap risk" rather than 5's minimal conflict risk.

4 / 5

Total

17

/

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/auth/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.