whoabuddy/claude-knowledge

This repository also configures its own agents. See what claude-knowledge tells them →

2Stars on the repository
34Mods indexed here, across every type
4mo agoLast push, which is what freshness is scored on
noneNo LICENSE: all rights reserved, so bodies are not copied

capture

05

whoabuddy/claude-knowledge

Skill Claude Code

Review session work and propose knowledge captures for human review. Scans git commits, changed files, and patterns used across repos to generate structured knowledge items. Includes review workflow to approve/reject/edit pending captures before persisting to the knowledge base.

not rated 2 4mo ago A 50 tokens

check-docs

07

whoabuddy/claude-knowledge

Skill Claude Code

Verify documentation quality - checks README.md, CLAUDE.md, and other docs for completeness and accuracy.

not rated 2 4mo ago A 24 tokens

daily-brief

10

whoabuddy/claude-knowledge

Skill Claude Code

Review logs from /logs and remote log APIs to provide orientation and context for the day. Use when starting a work session, checking what happened recently, or needing context on recent activity. Reads daily summaries, meeting notes, test runs, and worker logs.

not rated 2 4mo ago A 55 tokens

daily

11

whoabuddy/claude-knowledge

Skill Claude Code

Generate daily summary of git activity across all repositories.

not rated 2 4mo ago A 11 tokens

react-perf

17

whoabuddy/claude-knowledge

Skill Claude Code

React/Next.js performance optimization guidelines from Vercel Engineering. Use when reviewing performance, optimizing bundles, or fixing waterfalls.

not rated 2 4mo ago A 29 tokens

scrapyard

18

whoabuddy/claude-knowledge

Skill Claude Code

Play Floor is Lava on Scrapyard arena as Arc (arc0btc). Interactive AI agent game on Stacks.

not rated 2 4mo ago A 28 tokens

setup

19

whoabuddy/claude-knowledge

Skill Claude Code

Configure Claude Code with symlinks to knowledge base agents and skills.

not rated 2 4mo ago A 15 tokens

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: