alivebuild-extensions
FeaturedCreate new skills, rules, and hooks for your world. Checks plugin compatibility, writes to the human's space (not plugin cache), validates against the system, and suggests when repeated work should become a skill. For marketplace-ready plugins, hands off to the contributor plugin.
Install
Quality Score: 90/100
Skill Content
Details
- Author
- alivecontext
- Repository
- alivecontext/alive
- Created
- 6 months ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
alivesettings
The human wants to adjust how the system behaves — not what it contains, but how it feels. Voice, rhythm, preferences, walnut-level config, full permissions toggleable, named squirrel config, action logging toggle. The system adapting to them. Routes to preferences.yaml or walnut config.yaml depending on scope. For creating new skills, rules, or hooks, route to alive:build-extensions instead.
skill-creator
Create, review, rebuild, validate, and package Claude Code skills or plugins. Use when the user asks to make a skill, improve an existing skill, convert a workflow into a skill, design a plugin, scaffold plugin agents/hooks/MCP/LSP integrations, or prepare an uploadable Claude extension.
skill-builder
Use when the user is designing, reviewing or debugging a Claude Code skill and needs the judgment behind a good SKILL.md — should this even be a skill (vs CLAUDE.md / subagent / hook / MCP), why a description does or doesn't trigger, how to keep the body skimmable, how to package it. Carries the opinionated principles plus a review checklist. Trigger on "review my SKILL.md", "why doesn't my skill trigger", "principles of a good skill", "should this be a skill or a hook", "is my skill description good", even when the word "skill" is only implied. NOT for interactive scaffolding from scratch (use Anthropic's Skill Creator), nor for general coding.