From librarian
Use this skill for connecting to Telvok, managing auth, or when marketplace tools return auth errors. Triggers on: login, connect, authenticate, telvok account, api key.
How this skill is triggered — by the user, by Claude, or both
Slash command
/librarian:librarian-authThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Connect your Telvok account to access the marketplace, bounties, and publishing.
Connect your Telvok account to access the marketplace, bounties, and publishing.
auth({ action }) - Manage your Telvok connection
| Action | Description |
|---|---|
login | Start device code flow — returns a code and URL |
complete | Finish login after browser authorization |
status | Check if currently authenticated |
logout | Remove stored credentials |
auth({ action: "login" }) — Returns a code (e.g., "FBAM-57AJ") and URLauth({ action: "complete" }) — Saves API key locallyCredentials are stored in .librarian/.auth as JSON:
{
"api_key": "tvk_...",
"user_email": "[email protected]",
"user_id": "uuid",
"created_at": "...",
"expires_at": "..."
}
These tools require authentication:
library_buy() - Purchasing bookslibrary_publish() - Publishing booksbounty_create() / bounty_claim() / bounty_submit() - Bountiesmy_books() - Viewing your libraryseller_analytics() - Sales datarate_book() - Rating bookssync() - Syncing purchased contentmy_bounties() - Your bountiesfeedback() - Sending feedback"Authentication required" error:
Run auth({ action: "status" }) to check. If not connected, run auth({ action: "login" }).
Expired key:
API keys expire after 90 days. Run auth({ action: "login" }) to get a new one.
Wrong account:
Run auth({ action: "logout" }) then auth({ action: "login" }) with the correct account.
npx claudepluginhub joshuarweaver/cascade-knowledge --plugin telvokdev-librarianGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.