1.1K skills · sorted by relevance
Create or improve skills for Codewhale by defining their scope, writing clear activation descriptions and workflows, organizing supporting files, and checking discovery. It also helps decide when an external integration or automatic event handler is more appropriate.
Update context-mode from GitHub, rebuild and reinstall it, and configure hooks that connect it to the agent environment. Review the actual version and upgrade results in a checklist, then restart the session.
Understand how agentmemory automatically records tool activity, prompts, and session boundaries through hooks, actions triggered by session events. Use it to check integration setup, investigate missing records, and distinguish capture from optional summaries and context injection.
Create, configure, and troubleshoot Crush hooks, commands that run before tool execution. Use them to block or approve calls, rewrite tool input, or add context for the agent, with guidance on configuration and troubleshooting.
Build and improve React interfaces with guidance on component structure, hooks, state management, and Server Components. Review unnecessary rendering, extract reusable logic, and implement accessible forms and loading states using established React patterns.
Inventory hooks across the user, project, and project-local settings plus the ~/.claude/hooks scripts directory — read through the Agent Monitor Config Explorer API — and flag hooks that POST to the network or run arbitrary commands. Reads /api/cc-config/hooks and /api/cc-config/hook-scripts. Use when auditing hook safety.
The English summary is being prepared. Showing the original description.
Expert in Claude Code hooks - user-defined shell commands that execute at specific points in Claude Code's lifecycle. Provides guaranteed automation that doesn't rely on the LLM "remembering" to do something. Essential for enterprise workflows, code quality enforcement, and deterministic behavior in agentic coding. Use when "claude code hooks, automate claude, block tool use, pre tool use, post tool use, session start hook, claude lifecycle, claude-code, automation, hooks, lifecycle, cli, workflow, devtools" mentioned.
The English summary is being prepared. Showing the original description.
Cross-platform hooks reference for AI coding assistants — Claude Code, OpenAI Codex, GitHub Copilot, Cursor, Windsurf, and Amp. Covers hook authoring in Node.js (ESM and CJS) and Python, per-platform event schemas, inline-agent hooks and MCP in agent frontmatter, common JSON I/O, exit codes, best practices, and a fetch script to refresh docs from official sources. Use when writing, reviewing, or debugging hooks for any AI assistant.
The English summary is being prepared. Showing the original description.
Use when modifying agentic contextual building blocks like skills (SKILL.md), slash commands, agents, hooks, plugins, marketplaces, and instruction files (CLAUDE.md, AGENTS.md, GEMINI.md, QWEN.md, Cursor, Copilot, Cline, or Kiro rules), tool configuration such as an OpenCode `opencode.json`, Muse Code hooks (`.muse/hooks.json`), a Grok Build `.grok/` project layer or a Google Antigravity customization root (`.agents/`, `.agent/`, `_agents/`, `_agent/` — hooks, MCP config, rules, registries and plugins), and committed project memory (`.agents/memory/`). Run skillsaw on the files you touched, apply autofixes, resolve remaining violations with `skillsaw explain` guidance, and re-lint until clean before considering the work complete.
The English summary is being prepared. Showing the original description.
Generate platform-native hooks optimized for engagement, curiosity, and audience tension. Use when creating social media hooks, launch post openings, thread starters, video intros, founder story angles, or campaign first lines.
The English summary is being prepared. Showing the original description.
Generate, rank, and gate a reusable hook bank — sourced pains × named hook formula families, scored on clarity/specificity/curiosity/proof-backing, gated at the 10/16 ad threshold, delivered in 3 lengths with per-hook provenance and downstream routing. Use when "hook bank", "generate hooks", "hook generator", "write hooks for", "ad hooks", "scroll stoppers", "opening lines", "hook ideas", "first 3 seconds", "hook matrix", "I need 50 hooks", or any request to batch-produce attention-openers for ads, social, or video.
The English summary is being prepared. Showing the original description.
Generate opening hooks for content — "give me hooks for", "write hooks for this topic", "10 opening lines for". Returns 10 distinct hooks across different psychological angles using the named 2-Second Hook framework.
The English summary is being prepared. Showing the original description.
Set up automated checks before each Git commit using Husky and lint-staged. Format staged files with Prettier, run existing type checks and tests, and verify the setup using the repository's package manager.
Set up Claude Code hooks that block Git commands such as push, hard reset, and forced deletion before execution. Choose project-wide or global settings, customize the blocked commands, and verify that the hook rejects a test command.
Build a project-specific ECC installation plan from evidence in its code and configuration. Sort skills, rules, commands, and hooks into everyday components and references available when needed, then verify that the applied setup matches the project.
Audit Claude Code configuration with AgentShield to find exposed secrets, excessive permissions, unsafe hooks, and prompt injection risks, where malicious instructions influence an agent. Generate reports, apply supported automatic fixes, or create a security-focused starter configuration.
Write or repair React tests around user actions and visible results. Cover components and hooks, simulate network responses, check accessibility, and decide when real browser component tests or end-to-end tests across pages are needed.
Set up Plankton hooks in Claude Code to format and lint files after each edit. Route remaining violations to Claude for fixes, verify the results, and protect linter settings from changes that weaken checks.
Audit scheduled jobs, hooks, MCP servers, and external integrations using configuration files, logs, and recent runs. Distinguish configured tools from verified working ones, identify failures or overlap, and recommend what to keep, merge, remove, or fix next.
Build a project-specific ECC installation plan using evidence from code and configuration. Sort skills, rules, hooks, and other components into items loaded every session and references kept available for occasional use.
Group related code files by analyzing a graph of their connections with ruvector. Review group assignments, community labels, and links between files to understand code organization and investigate files that stand apart.
Set up Ruflo in a new repository using an interactive wizard or the standard preset. Create project instructions and configuration files, including MCP server registration so the agent can access the ruflo tools.
Test omo Codex Light edition in an isolated environment using real Codex and a local mock model. Verify installation, plugin hooks, and terminal startup, with captured evidence and no calls to a real model API.
Integrate FLUX image generation and editing into applications through the BFL API. The guide covers authentication, checking asynchronous results, completion notifications through webhooks, request limits, error handling, regional endpoints, and downloading generated images before their URLs expire.