Skip to main content
ClaudeWave

Skills de Claude Code · página 86

Skills individuales de Claude Code extraídas de todos los repositorios del directorio: cada SKILL.md, instalable con un comando, con su definición completa y las señales de confianza del repo.

13.377 skillsinstalación en 1 comando
  1. >

  2. >

  3. >

  4. >

  5. >

  6. >

  7. >

  8. >

  9. >

  10. plan349

    >

  11. >

  12. >

  13. >

  14. >

  15. >

  16. >

  17. >

  18. >

  19. >

  20. Extract .webarchive files (saved from Safari) into plain HTML/assets using the WebArchiveExtractor CLI. Use when the user wants to unarchive, extract, or convert a .webarchive file.

  21. Configure the OpenBSP plugin — check status, set org/account, manage allowed contacts, or force re-login. Use when the user asks to configure OpenBSP, check plugin status, manage contacts, or re-authenticate.

  22. Analyzes Rails applications and generates comprehensive upgrade reports with breaking changes, deprecations, and step-by-step migration guides for Rails 2.3 through 8.1. Use when upgrading Rails applications, planning multi-hop upgrades, or querying version-specific changes. Based on FastRuby.io methodology and "The Complete Guide to Upgrade Rails" ebook.

  23. Clean up after (or abandon) a Rails upgrade. Drop NextRails.next? and NextRails.current? branches and retire dual-boot scaffolding (Gemfile.next, Gemfile.next.lock, conditional Gemfile groups), keeping either the next or the current version. Trigger when the user says they are done with the upgrade, want to clean up dual-boot, want to drop NextRails branches, want to finish the upgrade, want to abandon or revert the upgrade attempt, want to roll back to the current Rails version, or want to pause this upgrade hop. Based on FastRuby.io's "Finishing an Upgrade" methodology, extended with an abandon/pause path.

  24. >

  25. >

  26. >

  27. >

  28. >

  29. >

  30. >

  31. >

  32. >

  33. >

  34. >

  35. >

  36. >

  37. >

  38. >

  39. >

  40. >

  41. >

  42. >

  43. >

  44. >

  45. >

  46. >

  47. >

  48. Persistent memory across sessions — recall, store, share, audit decisions, snapshots, and version history

  49. Analyze Mnemon harness eval reports, classify outcomes, and extract improvement evidence.

  50. Turn stable Mnemon harness eval findings into scoped project, loop, adapter, docs, or eval asset improvements.

  51. Design a scenario-driven Mnemon harness eval with target, hypothesis, HostAgent, loop configuration, evidence, and rubric.

  52. Execute or supervise a planned Mnemon harness eval run in an isolated HostAgent workspace.

  53. Manage project-scoped Mnemon goal state, evidence, verification, completion, blockers, and host goal links.

  54. Recall long-term memory from Mnemon when GUIDE.md indicates that prior memory may help the current task.

  55. Maintain prompt-facing working memory by editing MEMORY.md when GUIDE.md indicates that durable information should be kept.

  56. Draft or revise high-quality SKILL.md content for approved or proposed Mnemon skill changes.

  57. Start a low-frequency review of skill evidence and canonical skill lifecycle state.

  58. Apply approved skill lifecycle and content changes to the canonical Mnemon skill library.

  59. Record lightweight skill usage evidence when GUIDE.md indicates that a turn produced reusable workflow or lifecycle signal.

  60. Persistent memory CLI for LLM agents. Store facts, recall past knowledge, link related memories, manage lifecycle.

  61. Add persistent graph-based memory to NanoClaw agents using mnemon. Agents recall context before responding and remember insights after. Each group gets isolated memory with optional global shared store.

  62. Delegate coding work to Claude Code CLI for repository edits, reviews, and multi-turn implementation sessions.

  63. Delegate coding work to the OpenAI Codex CLI for repository changes, reviews, and focused fixes.

  64. gini341

    Gini's self-knowledge: how Gini configures, extends, and operates on its own state via /api/* and registered tools. Load when the user asks Gini about its own capabilities or asks Gini to modify its own configuration.

  65. Manage Apple Notes via memo CLI: create, search, edit.

  66. Apple Reminders via remindctl: add, list, complete.

  67. Move bytes between Gini upload space, external URLs, and workspace files. Used by every attachment / file-upload / file-download flow regardless of the target system (Linear, GitHub, S3, Notion, etc.).

  68. File a locally-captured, already-redacted Gini crash report as a GitHub issue, with the user's consent. Reads the pending crash queue and delegates the actual filing to the github-issues skill.

  69. Create, search, triage, label, assign, comment on, and close GitHub issues using the gh CLI, with a curl REST fallback.

  70. Detection engine for Gmail email watches: iterates the watch list, polls gws for new matching mail per watch, dedups, drops automated/self, and hands matches (labeled by sender) to the shared drafting turn. Provisioned and run automatically by the shared email-watch backing job.

  71. Sign a Google account into its own gws config dir and register it (tagged). Used by google-workspace-setup; runs the OAuth login + records the account.

  72. Google Calendar via gws: list events, create, accept, find free time.

  73. Google Docs via gws: read, append text, structured batch edits.

  74. Google Drive via gws: search, list, upload, download, share.

  75. Google Forms via gws: create forms, add items, read responses.

  76. Gmail via gws: send, read, search, label, draft, reply, forward.

  77. Google Meet via gws: create spaces, fetch join links, list recordings.

  78. Google Sheets via gws: read/write cells, append rows, structured batch edits.

  79. One-time setup for gws: install, OAuth, scopes, auto-approve.

  80. Read and write Linear issues, comments, projects, cycles, users, documents, initiatives, milestones, and more via the Linear MCP server. Attach chat-uploaded screenshots to issues.

  81. Build and maintain a company knowledge base as a wiki of interlinked markdown notes in the workspace — a private, compounding Wikipedia. Use when the user wants to start or organize a knowledge base / wiki, ingest sources (URLs, documents, pasted notes) into it, ask questions answered from it, or audit (lint) it. Defines the wiki layout (SCHEMA / index / log / raw / pages), the frontmatter contract, [[wikilink]] conventions, and a deterministic lint script that catches broken links, orphan pages, index drift, and frontmatter problems.

  82. Author a new SKILL.md from a user prompt, or migrate an existing non-spec skill to the Anthropic Agent Skills format.

  83. Install a pasted SKILL.md (or one fetched from a URL or file path) into the user-skill directory, reviewing risk and connector requirements.

  84. Turn LinkedIn connections (or any contact export) into a queryable personal CRM using the agent database.

  85. Place outbound AI phone calls via Bland AI: book reservations, make appointments, ask businesses questions, then report back the transcript and summary.

  86. |

  87. This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

  88. This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.

  89. This skill should be used when the user asks to "add MCP server", "integrate MCP", "configure MCP in plugin", "use .mcp.json", "set up Model Context Protocol", "connect external service", mentions "${CLAUDE_PLUGIN_ROOT} with MCP", or discusses MCP server types (SSE, stdio, HTTP, WebSocket). Provides comprehensive guidance for integrating Model Context Protocol servers into Claude Code plugins for external tool and service integration.

  90. This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin-name.local.md pattern for storing plugin-specific configuration with YAML frontmatter and markdown content.

  91. This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.

  92. This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.

  93. This skill should be used when generating spec artifacts (research.md, requirements.md, design.md, tasks.md), formatting agent output, structuring phase results, or when any Ralph agent needs guidance on concise, scannable output formatting. Applies to all Ralph spec phase agents.

  94. Core principle that the main agent is a coordinator, not an implementer. All work must be delegated to subagents.

  95. This skill should be used when the user asks about "ralph arguments", "quick mode", "commit spec", "max iterations", "ralph state file", "execution modes", "ralph loop", "coordinator behavior", "delegate to subagent", or needs guidance on Ralph plugin arguments, state management, delegation patterns, or execution loop behavior. Core behavioral skill for all Ralph Specum operations.

  96. Comprehensive understanding of the spec-kit methodology. Constitution-driven feature development with specify, plan, tasks, and implement phases.

  97. This skill should be used only when the user explicitly asks to use `$ralph-specum-cancel`, or explicitly asks Ralph Specum in Codex to stop execution or remove a spec.

  98. This skill should be used only when the user explicitly asks to use `$ralph-specum-design`, or explicitly asks Ralph Specum in Codex to run the design phase.

  99. This skill should be used only when the user explicitly asks to use `$ralph-specum-feedback`, or explicitly asks Ralph Specum in Codex to draft or submit feedback.

  100. This skill should be used only when the user explicitly asks to use `$ralph-specum-help`, or explicitly asks Ralph Specum in Codex for help or command guidance.