auth

Epicenter auth packages: `@epicenter/auth` and the Svelte wrapper at `@epicenter/svelte/auth`, OAuth sessions, identity state, auth-owned fetch/WebSocket, and the reload gate that makes a page lifetime one auth generation. Use when editing Epicenter auth clients, session state, hosted sign-in, or how a route boots from auth.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/auth/SKILL.md

Quality

Content

65%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, well-organized architectural reference packed with concrete code, paths, and guardrails. Its weaknesses are verbosity from cross-section repetition and a monolithic single-file structure with no progressive disclosure into bundle files.

Suggestions

Consolidate the repeatedly-stated invariants (e.g., that only the instance-token client drives a live connection.status) into one canonical statement and reference it, to reduce token cost.

Split the large type definitions and the server composition/Hono pipeline into reference files under references/ and link to them from SKILL.md to improve progressive disclosure.

Add an explicit step-by-step workflow with validation checkpoints for the most common editing task (e.g., adding or changing a credential client), so the procedural path is as clear as the reference material.

Dimension	Reasoning	Score
Conciseness	The body is dense with domain-specific Epicenter detail and avoids explaining basics Claude already knows, but at ~590 lines it repeats several key invariants across sections (e.g., the live-connection-status fact appears multiple times) and could be tightened.	3 / 5
Actionability	Concrete executable code, exact file paths, full type definitions, named guards, and a 'Common Pitfalls' list provide copy-paste-ready guidance across the common cases.	5 / 5
Workflow Clarity	This is primarily a reference/architecture document rather than a sequenced procedure; the 'Upstream Grounding' section does include a verify-before-changing-code checkpoint, but most content lacks an explicit multi-step sequence with validation.	3 / 5
Progressive Disclosure	The body is well-sectioned with clear headers, but it is a monolithic ~590-line single file with no bundle files or external references, and content such as large type definitions and the server composition that could live in separate files is inlined.	3 / 5
	Total	14 / 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, concrete description that names specific packages and surfaces, includes an explicit 'Use when...' trigger clause, and is tightly scoped to a distinct niche. It is third-person and free of vague fluff.

Dimension	Reasoning	Score
Specificity	Names concrete components (`@epicenter/auth`, `@epicenter/svelte/auth`, OAuth sessions, identity state, auth-owned fetch/WebSocket, reload gate) and several specific actions, with only minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what (the package surface and its components) and when (a 'Use when...' clause with concrete trigger phrases), matching the top anchor.	5 / 5
Trigger Term Quality	The 'Use when editing Epicenter auth clients, session state, hosted sign-in, or how a route boots from auth' clause supplies natural trigger phrases a user would actually say, though a few synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	Scoped to the clearly distinct 'Epicenter auth' niche with package-scoped triggers, making overlap with other skills minimal.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (598 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: EpicenterHQ/epicenter
Path: .agents/skills/auth/SKILL.md
Commit: 9e1f9d2

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.