Claude Skills by runkids

github.com/runkids

21 skillsA× 19B× 20 installs9 views

SkillshareAManage skills, agents, extras, hooks, plugins, and MCP connection settings with the Skillshare CLI. Use when the user asks to configure or run Skillshare, install or sync resources across AI tools, manage shared memory notes, import MCP settings, manage targets, audit skills, recover backups, or troubleshoot Skillshare configuration and sync. Covers global and project modes, noninteractive automation, and guidance for the terminal UI.developmentgobashVotes: 0GitHub stars: 2,714
Skillshare ChangelogAGenerate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed since last release", this is the skill to use. Do NOT manually edit CHANGELOG.md without this skill — it ensures proper formatting, user-perspective writing, and website changelog s...developmentpythongoVotes: 0GitHub stars: 2,714
Skillshare Cli E2e TestBRun isolated E2E tests in devcontainer from ai_docs/tests runbooks. Use this skill whenever the user asks to: run an E2E test, execute a test runbook, validate a feature end-to-end, create a new runbook, or test CLI behavior in isolation. If you need to run a multi-step CLI validation sequence (init → install → sync → verify), this is the skill — it handles ssenv isolation, flag verification, and structured reporting. Prefer this over ad-hoc docker exec sequences for any test that follows a r...developmentpythongoVotes: 0GitHub stars: 2,714
Skillshare Codebase AuditACross-validate CLI flags, docs, tests, and targets for consistency across the codebase. Use this skill whenever the user asks to: audit the codebase, check for consistency issues, find undocumented flags, verify test coverage, validate targets.yaml, check handler split conventions, or verify oplog instrumentation. This is a read-only audit — it reports issues but never modifies files. Use after large refactors, before releases, or whenever you suspect docs/code/tests have drifted out of sync.developmentpythongoVotes: 0GitHub stars: 2,714
Skillshare DevcontainerARun CLI commands, tests, and debugging inside the skillshare devcontainer. Use this skill whenever you need to: execute skillshare CLI commands for verification, run Go tests (unit or integration), reproduce bugs, test new features, start the web UI, or perform any operation that requires a Linux environment. All CLI execution MUST happen inside the devcontainer — never run skillshare commands on the host. If you are about to use Bash to run `ss`, `skillshare`, `go test`, or `make test`, stop...developmentpythongoVotes: 0GitHub stars: 2,714
Skillshare Implement FeatureAImplement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare. This skill enforces test-first development, proper handler split conventions, oplog instrumentation, and dual-mode (global/project) patterns. If the request involves writing Go code and tests, use this skill — even if the user...developmentpythongoVotes: 0GitHub stars: 2,714
Skillshare ReleaseAPrepare and review skillshare releases using the Release Please PR, verify the proposed version and changelog, inspect draft assets, and publish through the manual Publish Release workflow when explicitly authorized. Use when the user says "release", "prepare release", "cut a release", or asks to publish a new version. For changelog-only tasks, use /changelog instead.developmentpythongoVotes: 0GitHub stars: 2,714
Skillshare Ui Website StyleASkillshare frontend design system for the React dashboard (ui/) and Docusaurus website (website/). Use this skill whenever you: build or modify a dashboard page or component in ui/src/, style or layout website pages or custom CSS in website/, create new React components for the dashboard, add pages to the dashboard, fix visual bugs in either frontend, or need to know which design tokens, ss-* classes, components, or patterns to use. Covers the two dashboard styles (Clean / Playful) in light a...developmentpythongoVotes: 0GitHub stars: 2,714
Skillshare Update DocsAUpdate website docs to match recent code changes, cross-validating every flag against source. Use this skill whenever the user asks to: update documentation, sync docs with code, document a new flag or command, fix stale docs, or update the README. This skill covers all website/docs/ categories (commands, reference, understand, how-to, troubleshooting, getting-started) plus the built-in skill description and README. If you just implemented a feature and need to update docs, this is the skill ...developmentpythongoVotes: 0GitHub stars: 2,714
TestdataAA perfectly safe skill for testingdevelopmenttestingVotes: 0GitHub stars: 2,714
BlogA--- Brief overview of what this skill does and its value. ```developmentgobashVotes: 0GitHub stars: 2,714
Skillshare Windows UtmBVerify skillshare on a real Windows guest running in local UTM: build a pinned commit in the devcontainer, push it into the VM, and either run the Windows E2E runbook with full and basic-user tokens or hand the maintainer a one-line hands-on setup. Use this whenever a change touches Windows links, junctions, file symlinks, Developer Mode, copy fallback, Windows paths, or the dashboard on Windows, or when the user asks to test or accept something on Windows / UTM.ai-agentspythonrustVotes: 0GitHub stars: 2,714
Agents Context RouterASplit a bloated AGENTS.md / CLAUDE.md / README into a small always-loaded kernel plus task-routed wiki topics, loaded on demand by a zero-dependency script (`scripts/ai-context.py list|<topic>|check`) with byte budgets, so agents stop burning their context window on docs unrelated to the task. Use this skill whenever the user says AGENTS.md or CLAUDE.md is too long, too big or loads too much context; asks to split, slim, reorganize, route or "wiki-fy" repo docs or agent instructions; wants a ...ai-agentspythongoVotes: 0GitHub stars: 14
Feature Radar ArchiveAArchive a completed, rejected, or covered feature into .feature-radar/archive/ with mandatory learning extraction. MUST use this skill whenever a feature reaches a terminal state — done, rejected, covered, deferred, or N/A — including casual mentions like "we shipped X". The skill extracts learnings, derives new opportunities, and updates refs. Use when the user reports a feature shipped or finished, decides against building one, defers or postpones one, or asks to close or archive an opportu...ai-agentsgoVotes: 0GitHub stars: 14
Feature Radar LearnAExtract reusable patterns, architectural decisions, and pitfalls from completed work into .feature-radar/specs/. Captures the "why" behind choices so future sessions build on past experience. MUST use this skill when the user reflects on what worked or didn't, wants to record a decision or pattern for future use, or hit a dead end worth documenting. Use when the user asks to remember, document, or extract lessons from recent work. Do NOT use for recording external observations — that's featur...ai-agentsgoVotes: 0GitHub stars: 14
Feature Radar RefARecord external observations, ecosystem trends, and creative inspiration into .feature-radar/references/. MUST use this skill when the user mentions something interesting from outside their project — other tools, articles, approaches, or trends — even casually ("I saw a cool thing in X"). Use when the user shares a URL, article, talk, or research finding, notes an ecosystem trend or a related project's notable feature, or asks to bookmark or track external inspiration. Do NOT use for internal...ai-agentsgogitVotes: 0GitHub stars: 14
Feature Radar ScanADiscover new feature opportunities from creative brainstorming, user feedback, ecosystem trends, and cross-project research. Writes results to .feature-radar/opportunities/. MUST use this skill when the user wants to GENERATE new ideas — not evaluate existing ones — including casual or half-formed ones ("what if we...", "I have an idea"). Use when the user wants feature ideas or new directions, asks what the project is missing, wants to mine issues, community feedback, or adjacent tools for i...ai-agentsgoapiVotes: 0GitHub stars: 14
Feature Radar ValidateAValidate SKILL.md frontmatter and .feature-radar/ files against format rules. Runs validate.sh, reports errors/warnings, and auto-fixes issues. MUST use this skill after editing any SKILL.md or .feature-radar/ file, even if the user doesn't ask — catches format bugs like the Agent Skills spec's 1024-char description limit before they break the skill. Use when the user asks to validate, lint, or verify skills or .feature-radar/ files, after editing either, or before committing changes that tou...ai-agentsbashVotes: 0GitHub stars: 14
Feature RadarAFull-cycle feature discovery, evaluation, and prioritization. Builds a persistent knowledge base at .feature-radar/ and runs a 6-phase workflow to recommend what to build next. Modes: full (all phases), quick (scan only), evaluate (prioritize), #N (deep-dive one). MUST use this skill whenever the user asks about feature priorities, roadmaps, what to build, or wants to evaluate/compare feature ideas — even if they don't say "feature radar" explicitly. Use when the user wants to decide what to ...ai-agentsgorailsVotes: 0GitHub stars: 14
React DoctorAUse when finishing a feature, fixing a bug, before committing React code, or when the user types `/doctor`, asks to scan, triage, or clean up React diagnostics. Covers lint, accessibility, bundle size, architecture. Includes a regression check and a full local-triage workflow that fetches the canonical playbook.ai-agentsgobashVotes: 0GitHub stars: 14
DeployADeploy Tidepool to production. Use when the user asks to deploy, release or ship.ai-agentsgitVotes: 0GitHub stars: 3