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.

9 stars 4 forksSecurity

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add jscraik/Agent-Skills --skill best-practices
Manual install
git clone --depth 1 https://github.com/jscraik/Agent-Skills.git /tmp/Agent-Skills
mkdir -p ~/.claude/skills
cp -r /tmp/Agent-Skills/Skills/security-ops/best-practices ~/.claude/skills/best-practices

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Better Auth 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.

## Philosophy
- Keep the workflow evidence-first and bounded to the requested scope.
- Prefer the smallest reversible step that proves or disproves the current assumption.
- Preserve user work and repo-native contracts before introducing new machinery.

## When To Use
- Reviewing existing Better Auth setup.
- Finding auth, session, provider, plugin, and deployment risks.
- Recommending small secure remediations.

## Avoid
- Unrelated work that belongs to a more specific skill.
- Broad rewrites before the first blocker or decision point is understood.
- Claiming success without command, artifact, or decision evidence.

## Inputs
- auth integration files
- providers
- session config
- deployment context
- known symptom

## Outputs
- security findings
- risk priority
- minimal remediation
- validation checks
- Schema-bound outputs include `schema_version`.

## Workflow
1. Classify the requested mode and collect only the missing critical inputs.
2. Inspect 2-3 focused surfaces before expanding scope.
3. Take the smallest action that advances the confirmed goal.
4. Stop at the first failed gate or blocker and report exact evidence.
5. Rerun the relevant validation after fixes before claiming completion.

## Security Constraints
Read the full skill on GitHub

Details

Skill name
best-practices
Path
Skills/security-ops/best-practices/SKILL.md
License
Apache-2.0
Repo updated
16 November 2026

FAQ

What does the Best Practices skill do?

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.

How do I install the Best Practices skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add jscraik/Agent-Skills --skill best-practices. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Best Practices popular?

It lives in jscraik/Agent-Skills, which has 9 GitHub stars and 4 forks.

Related skills

Browse the most popular Claude skills, all security skills, or write your own with the skills generator.