All authors

Claude Skills by valsteen
github.com/valsteen8 skills0 installs5 views
- Maintaining Agent GuidanceUse when establishing or evaluating a project's durable AI-facing guidance, recommending what guidance it needs, resolving unclear ownership, or untangling duplicated or conflicting instructions. Do not use for routine wording, link, or metadata corrections when the authoritative owner is already settled.Votes: 0GitHub stars: 2
- Pinboard DeliverDeliver exactly one active pinboard attempt from its accepted brief, current definition identity, and renewable lease. Use when the item, checkout, definition, acceptance criteria, and verification are already recorded. Do not use for intake, portfolio selection, broad audits, design exploration, or acceptance review.Votes: 0GitHub stars: 2
- Pinboard IntakePreserve one newly proposed piece of project work as a ready item on the pinboard. Use when the user explicitly asks to add, queue, intake, preserve, save for later, or send a prerequisite, bug, cleanup, feature, contradiction, or clarification for later work, including when no board exists yet. Do not use merely because a conversation explores an idea.Votes: 0GitHub stars: 2
- PinboardUse before answering status, planning or ideation about saved Pinboard work, including quick read-only status, or any product, roadmap or architecture discussion in a Pinboard-managed project. Coach discussion points and preserve decisions even when no implementation is requested. Also coordinate next-work selection, parallel work, worker dispatch and continuation, lifecycle, review, recovery and long-running continuity. Do not implement an assigned worker attempt; use $pinboard-deliver.Votes: 0GitHub stars: 2
- Repository ReadinessAssess whether an unfamiliar repository can be changed reliably by mapping semantic authority through consumers, projections, and validation, then make only authorized improvements. Use for onboarding vibe-coded, inherited, or long-lived multi-team codebases, or requests to make a project agent-ready, assess agentic readiness, or perform a readiness check. Do not use for a known cleanup-only task or a routine guidance correction with an already settled owner.Votes: 0GitHub stars: 2
- Slop CleanupRemove code or features cleanly by finding and collapsing every orphaned production path, test-only API, stale variant, archaeological name, document, dependency, and tool. Use for any code cleanup that deletes behavior or structure, scaling from a local residue check to a repository-wide fixed-point pass. Do not use for additive work, formatting-only changes, routine prose corrections, or a general repository-readiness assessment.Votes: 0GitHub stars: 2
- Technical WritingShape or edit substantial technical documents and human-facing project artifacts, including RFCs, design notes, investigation reports, decision records, briefs, results, reviews, and pull-request descriptions. Use collaborative composition when the author is still making material choices, and quiet editorial production when accepted facts are sufficient. Also use when explicitly invoked for ambiguous document work. Do not use for routine Pinboard coordination, minor copy edits, or generic cod...Votes: 0GitHub stars: 2
- Investigation FocusGuide a substantial evidence-led investigation, whether the requested result is already clear or the human needs to narrow a diffuse question, retain context across sessions, or make several decision-ready outputs. Do not use for ordinary repository delivery or a one-off factual answer.Votes: 0GitHub stars: 2