best-practices

Audit, review, and harden Better Auth integrations. Use when the user wants Better Auth security review, config debugging, provider hardening, session checks, or operational risk guidance.

Quality

88%

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

85%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 tight, well-structured review skill with strong conciseness and an explicit validated workflow. Its main weakness is progressive disclosure: the referenced deferred paths do not map to real bundle files, so the navigation cannot be followed.

Suggestions

Make the Progressive Disclosure references resolve to actual files under references/ (or use relative paths to existing bundle files like references/contract.yaml and references/evals.yaml) so navigation is verifiable.

Add 1-2 concrete example commands or a short code snippet in the Validation section to lift actionability from directive-level to copy-paste ready.

Confirm the archived-source path exists in the bundle or mark it clearly as an external/infrastructure dependency to avoid a dead reference.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no concept over-explanation; assumes Claude knows what Better Auth is and every line is actionable guidance that earns its place.	5 / 5
Actionability	Concrete procedural directives ('Inspect 2-3 focused surfaces', 'Rerun the relevant validation after fixes', 'Redact credentials... by default') are specific, but guidance stays at the directive level rather than copy-paste commands, leaving minor gaps.	4 / 5
Workflow Clarity	A numbered 5-step workflow with explicit fail-fast gates ('Stop at the first failed gate'), feedback loops ('rerun the same check'), and dedicated Validation/Failure Mode sections providing checklists and error recovery.	5 / 5
Progressive Disclosure	The body is appropriately split and the Progressive Disclosure section signals one-level-deep deferred references, but the cited paths (Infrastructure/references/...) do not resolve to files present in this skill's references bundle, so navigation is not actually verifiable.	3 / 5
	Total	17 / 20 Passed

Description

92%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 well-crafted description that clearly states capabilities and explicit trigger conditions with strong natural phrasing. Minor room to expand trigger synonyms, but overall highly specific and complete.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('audit, review, and harden') plus a comprehensive set of capabilities (security review, config debugging, provider hardening, session checks, operational risk guidance) with no vague padding.	5 / 5
Completeness	Explicitly answers both 'what' (audit/review/harden Better Auth integrations) and 'when' via a concrete 'Use when the user wants...' clause listing multiple triggers.	5 / 5
Trigger Term Quality	Strong natural phrasing users would actually say ('Better Auth security review', 'config debugging', 'provider hardening'), with good synonym coverage; falls just short of the fully exhaustive 5-anchor list that also captures every common variation.	4 / 5
Distinctiveness Conflict Risk	Anchored to a clear niche ('Better Auth integrations') with domain-specific triggers that minimize overlap risk with other skills.	5 / 5
	Total	19 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: jscraik/Agent-Skills
Path: Skills/security-ops/best-practices/SKILL.md
Commit: f1f2f21

Reviewed: ~8 hours 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.