ace8991
Community@ace8991
ace8991 provides Claude Code plugin development skills covering commands, hooks, agents, MCP servers, plugin scaffolding, and Opus 4.5 model migration.
Agent Skills by ace8991
Showing 10 vetted skills indexed across 1 GitHub repositories.
ace8991claude-opus-4-5-migration
Migrate model strings and prompts from Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5.
ace8991Command Development
Create Claude Code slash commands with frontmatter, arguments, file references, and bash execution.
ace8991Skill Development
Guides creation of Claude Code plugin skills with progressive disclosure structure.
ace8991Plugin Settings
Implements per-project plugin configuration using .claude/plugin-name.local.md files with YAML frontmatter.
ace8991Plugin Structure
Guides creation of Claude Code plugins with manifest configuration and component organization.
ace8991Hook Development
Create and validate event-driven hooks for Claude Code plugins using prompt-based and command configurations.
ace8991MCP Integration
Configure Model Context Protocol servers in Claude Code plugins for external service integration.
ace8991Agent Development
Create and validate Claude Code plugin agents with frontmatter, system prompts, and triggering examples.
ace8991frontend-design
Generates production-grade frontend interfaces with distinctive typography, color, motion, and layout choices.
ace8991Writing Hookify Rules
Create hookify rule files with YAML frontmatter and regex patterns for hook events.
Frequently Asked Questions About ace8991
FAQPage SchemaWhat tasks can I accomplish using ace8991's skills?▼
You can scaffold Claude Code plugins, create slash commands with YAML frontmatter, build subagents, implement event-driven hooks, integrate MCP servers over SSE/stdio/HTTP/WebSocket, configure plugin settings via .local.md files, write hookify rules, and migrate prompts to Opus 4.5.
Who are these skills designed for?▼
These skills target developers building Claude Code plugins and extensions. They suit engineers creating custom slash commands, autonomous subagents, hook-based validation, or MCP server integrations, plus teams upgrading existing codebases from Sonnet 4.0 or Opus 4.1 to Opus 4.5.
How do the plugin structure and settings skills work in practice?▼
The plugin-structure skill guides directory layout, plugin.json manifest configuration, and ${CLAUDE_PLUGIN_ROOT} usage for auto-discovery. The plugin-settings skill documents the .claude/plugin-name.local.md pattern, storing per-project configuration as YAML frontmatter with markdown content.
What hook events and MCP server types are supported?▼
Hook development covers PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, and Notification events, including prompt-based hooks. MCP integration supports SSE, stdio, HTTP, and WebSocket server types configured via .mcp.json.
Are there licensing terms or limitations to know about?▼
The frontend-design skill references complete license terms in its bundled LICENSE.txt file. The Opus 4.5 migration skill explicitly does not handle Haiku 4.5 migrations. Other skills carry version numbers (0.1.0–0.2.0) indicating early-stage releases.