بنقرة واحدة
marketplace
يحتوي marketplace على 25 من skills المجمعة من goodfoot-io، مع تغطية مهنية على مستوى المستودع وصفحات skill داخل الموقع.
Skills في هذا المستودع
You must load this skill if you are creating or updating standalone documentation.
This skill should be used when the user asks to "skillify this", "turn this into a skill", "make a skill out of what we just did", "generalize this task into a reusable skill", or otherwise wants to capture a just-completed session task as a new skill or fold it into an existing one.
Browser automation using the puppeteer NPM package. Use when performing tasks on websites as a user would, taking screenshots, filling forms, or navigating web applications.
Load this skill immediately after a user mentions "@goodfoot/claude-code-hooks" or Claude Code hooks.
Load this skill immediately after a user mentions "@goodfoot/codex-hooks" or Codex hooks.
Load this skill immediately after a user mentions "@goodfoot/codex-hooks" or Codex hooks.
Identify and remove git worktrees (and their branch refs) whose work has already landed in the main branch, including squash- and rebase-merged ones that naive ancestry checks miss. Use when the user says "prune merged worktrees", "clean up worktrees", "remove stale worktrees", "worktree cleanup", or asks which worktrees have no unique commits.
Troubleshooting and detailed usage for the voice MCP server — browser/audio problems, conversation lifecycle (pause/resume/reset), context management, intervening when the avatar is wrong, the full-viewport HTML stage, ending a session, and startup/channel failures. Load a reference below when a live voice conversation needs deeper handling than the start message covers, or when something is not working.
Use puppeteer to browse websites
Use for failure-mode analysis
Comprehensive failure analysis methodology for extracting learnings from implementation failures, test failures, and validation errors.
Conduct empirical technical investigations using isolated subagents to compare alternatives or validate assumptions through prototype testing.
Run `npx jsdoczoom -h` for help
Run `npx jsdoczoom --skill` for a style guide
Analyze TypeScript codebase health with metrics for complexity, coupling, duplication, cycles, data flow, and swallowed errors. Use when: (1) assessing code quality before refactoring, (2) identifying complexity hotspots, (3) finding duplicate code to extract, (4) detecting circular dependencies, (5) finding unused parameters or swallowed errors, (6) generating health reports for a codebase.
Use `npx @goodfoot/claude-code-skill-reader <skill-name>` to read and process Claude Code skill and command files from project, plugin, and marketplace sources. This skill should be used when Claude needs to inspect, read, or trace how a skill or command is resolved.
Migrate Claude Code hook implementations to use @goodfoot/claude-code-hooks.
Structured project plan format with required sections and examples.
GitHub operations using the octokit NPM package. Use when creating issues, managing pull requests, reading repository files, searching code, or interacting with GitHub Actions workflows.
Gmail operations using the googleapis NPM package. Use when sending, reading, searching, or organizing emails programmatically. Handles drafts, labels, threads, filters, and attachments through Google's official SDK.
Reference for Linear webhooks and TypeScript SDK. Use when receiving Linear webhook payloads, responding to issues or comments, changing issue status, or querying Linear state via the @linear/sdk package.
Decision routing for complex refactoring scenarios. Directs to supplementary methodology documents when nuanced judgment is needed during plan-aware code cleanup.
Evidence-based explanation techniques for technical documentation. Use when creating documentation, explaining systems, or choosing the right approach for technical communication needs.
Reusable documentation components for technical writing. Use when structuring technical documentation, creating user guides, or needing consistent formatting patterns for explanations, comparisons, code examples, diagrams, and troubleshooting workflows.
Adds the plugin directory to the context.