Heartwood Auth
ListedAuthenticates users against legacy systems using biometrics and contextual data, minimizing password reliance.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add autumnsgrove/lattice --skill heartwood-auth -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
autumnsgrove
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: auth-api.grove.place.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
Hosts contacted
auth-api.grove.placeundeclaredWhat it found (3 of 5)
- .claude/skills/heartwood-auth/SKILL.md:73contacts auth-api.grove.place
const response = await fetch("https://auth-api.grove.place/api/auth/session", { - .claude/skills/heartwood-auth/SKILL.md:109contacts auth-api.grove.place
const tokens = await fetch("https://auth-api.grove.place/token", { - .claude/skills/heartwood-auth/SKILL.md:123contacts auth-api.grove.place
const user = await fetch("https://auth-api.grove.place/verify", {
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned autumnsgrove/groveengine at edebdc71a7.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- edebdc71a7
- Scanned
- 1 file, 358 lines
About this skill
What it does
The Heartwood Auth skill enables AI agents to integrate authentication into Grove applications, protecting routes and validating user sessions. It leverages Grove's centralized authentication service (Heartwood), powered by Better Auth, offering features like OAuth sign-in with Google, magic links via Resend, passkeys for passwordless authentication, and cross-subdomain single sign-on. The skill provides multiple integration options to suit both new and existing applications within the .grove.place domain.
When to use it
This skill is useful in these scenarios:
- Adding authentication to a new Grove application.
- Protecting administrative routes within an application.
- Validating user sessions after login.
- Setting up OAuth sign-in using Google.
- Integrating with the existing Heartwood (GroveAuth) infrastructure.
Key capabilities
- OAuth Providers: Google
- Magic Links: Click-to-login emails via Resend
- Passkeys: WebAuthn passwordless authentication
- KV-Cached Sessions: Fast session validation (sub-100ms)
- Cross-Subdomain SSO: Single sign-on across all
.grove.placesubdomains - Multiple integration options: Better Auth Client, Cookie-Based SSO, and Legacy Token Flow
Example prompts
Here are some example prompts for an AI agent using the Heartwood Auth skill:
- "Authenticate this user with Google OAuth."
- "Validate the current session token."
- "Sign out the logged-in user."
- "Generate a magic link for passwordless login."
Tips & gotchas
- For new integrations, using the Better Auth Client (as shown in the source code) is recommended.
- Apps on
.grove.placesubdomains can leverage automatic session handling via cookies. - Existing integrations might need to use the Legacy Token Flow for backwards compatibility.