From librarian
Use this skill for knowledge bounties — creating, claiming, or fulfilling bounty requests. Triggers on: bounty, reward, knowledge request, fulfill, claim bounty.
How this skill is triggered — by the user, by Claude, or both
Slash command
/librarian:librarian-bountiesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create and fulfill knowledge bounties on Telvok. Post what you need, reward who delivers.
Create and fulfill knowledge bounties on Telvok. Post what you need, reward who delivers.
bounty_create(title, amount_cents, description?, tags?, expires_days?) - Post a knowledge requestbounty_list(query?, tags?, status?, limit?) - Browse available bountiesbounty_claim(bounty_id) - Claim a bounty to fulfillbounty_submit(bounty_id, book_slug) - Submit your published book as fulfillmentmy_bounties(role?) - View your created and claimed bountiesCreator: bounty_create() → Pay via Stripe → Bounty goes live
↓
Claimer: bounty_list() → bounty_claim() → library_publish() → bounty_submit()
↓
Creator: Review submission → Approve (payment released) or Reject (with reason)
↓
If no response in 7 days → Auto-approved
bounty_create({
title: "Stripe webhook patterns",
amount_cents: 1000, // $10 minimum $5
description: "Need idempotency and retry handling examples",
tags: ["stripe", "webhooks"],
expires_days: 30 // Default: 30
})
Returns a Stripe checkout URL. Bounty becomes visible after payment.
Platform fee: 20% (claimer receives 80%).
bounty_list({ query: "stripe" }) - Find bounties you can fulfillbounty_claim({ bounty_id: "abc123..." }) - Claim it (locks out others)record(), then library_publish() as a bookbounty_submit({ bounty_id: "abc123...", book_slug: "my-stripe-patterns" })my_bounties() // All your bounties
my_bounties({ role: "creator" }) // Bounties you posted
my_bounties({ role: "claimer" }) // Bounties you're fulfilling
auth({ action: "login" }))Guides 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.
npx claudepluginhub joshuarweaver/cascade-knowledge --plugin telvokdev-librarian