auth

Epicenter auth packages: `@epicenter/auth` and the Svelte wrapper at `@epicenter/svelte/auth`, OAuth sessions, identity state, auth-owned fetch/WebSocket, and workspace boot selection. Use when editing Epicenter auth clients, session state, hosted sign-in, or auth/workspace integration.

Quality

96%

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

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable, well-sequenced architecture documentation that assumes Claude's competence and packs in concrete code, paths, and validation checkpoints. Its main weakness is monolithic structure — large reference-grade sections are inlined rather than split into separate files.

Suggestions

Split the detailed type definitions (Public Surface, Persisted Cell) and the server route composition into reference files (e.g. references/types.md, references/server-routes.md) and link to them from SKILL.md to reduce the monolithic wall.

Move the machine-auth/CLI daemon section into a dedicated reference file since it is a distinct surface not needed for the common hosted-auth case.

Consider extracting the Common Pitfalls list into a references/pitfalls.md so the overview stays lean while the do-not-do guidance remains discoverable one level deep.

Dimension	Reasoning	Score
Conciseness	Dense project-specific knowledge (exact file paths, plugin configs, internal types) with no generic concept explanations and code blocks explicitly 'trimmed of JSDoc'; it assumes competence and nearly every token earns its place.	3 / 3
Actionability	Provides copy-paste-ready TypeScript (createOAuthAppAuth, auth.fetch, openCollaboration), exact type definitions, concrete plugin config values (accessTokenExpiresIn: 600, requirePKCE: true), and specific file paths to route through.	3 / 3
Workflow Clarity	Multi-step flows are sequenced with explicit validation checkpoints — the network gate branch table, the fail-closed offline invariant, the same-principal guard, and the revocation mitigation unit with 401-vs-503 error classification and reconnect feedback loops.	3 / 3
Progressive Disclosure	The body is a ~580-line monolith with no bundle files and no offloaded references; detailed type definitions, server route composition, and CLI/daemon sections could live in separate reference files but are instead inlined.	2 / 3
	Total	11 / 12 Passed

Description

100%

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 tight, third-person description that names concrete packages and capabilities and pairs them with an explicit 'Use when' trigger clause. It is specific, complete, and unlikely to conflict with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities with exact package paths (`@epicenter/auth`, `@epicenter/svelte/auth`), OAuth sessions, identity state, auth-owned fetch/WebSocket, and workspace boot selection — no vague language.	3 / 3
Completeness	Explicitly answers both what (Epicenter auth packages and their capabilities) and when ('Use when editing...') with explicit trigger guidance.	3 / 3
Trigger Term Quality	The 'Use when editing Epicenter auth clients, session state, hosted sign-in, or auth/workspace integration' clause uses natural terms a user of this codebase would actually say.	3 / 3
Distinctiveness Conflict Risk	Scoped to named Epicenter auth packages with branded paths, giving it a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	12 / 12 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 (589 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

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

Reviewed: 3 days 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.