fen-maintainer
Development and maintenance toolkit for the Fen codebase.
Install
mkdir -p .claude/skills/fen-maintainer && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18095" && unzip -o skill.zip -d .claude/skills/fen-maintainer && rm skill.zipInstalls to .claude/skills/fen-maintainer
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Develop, test, and maintain the Fen repository.Key capabilities
- →Develop Fennel source code
- →Manage launcher and development workflows
- →Maintain documentation and tests
- →Manage extensions for the Fen repository
- →Run focused tests by file, directory, or name
- →Reload source edits during interactive runs
How it works
The skill provides workflows and commands for developing, testing, and maintaining the Fen repository, including source-checkout development and test execution.
Inputs & outputs
When to use fen-maintainer
- →Run Fen tests
- →Manage extensions
- →Execute launcher development workflow
- →Reload source edits
About this skill
Fen Maintainer
AGENTS.md is already in context and holds the workflow, hot-reload invariants, and gotchas.
This skill adds where to look next and the checks people forget.
Read before changing
| Change | Read |
|---|---|
| Structure, new modules, cross-extension helpers | docs/architecture.md#design-principles |
| Test runner flags, smoke, graphs, profiling, reload rules | docs/development.md |
| Extensions, manifests, register kinds, reload lists | docs/extensions.md |
| Built-in tools | docs/tools.md |
| Providers and model config | docs/providers.md |
| TUI behavior or layout | docs/tui.md, then the ux-testing skill for tests |
| Nix artifacts and releases | docs/distribution.md |
| Review rules by path | .github/copilot-instructions.md, .github/instructions/*.instructions.md |
Validation ladder
Follow docs/development.md#contributing-changes for integration and validation policy.
Do not require a PR or full source suite for every edit.
For source/build changes, run the smallest useful check while iterating and make check before integration:
fennel scripts/test/fennel-check.fnl
make test TESTS=path/to/focused_test.fnl
make fmt
make check
For docs/prompt-only changes, review the diff and run git diff --check plus relevant doc checks.
For test-only changes, run affected tests; broaden checks for shared harness changes.
A command killed by a timeout has not passed; rerun it or say so.
Checks people forget:
- Added, moved, or removed a module: run
make graphsand commit the regenerateddocs/graphs/output, ormake checkfails. - Added a first-party extension or module: update its manifest and
reload-moduleslist. - Changed a Make target: keep it usable without Nix unless its name says
nix. - Touched packaging or the binary path:
nix build .#fen --no-link, thenrm -f result result-*if you built with a link.
When not to use it
- →When hand-editing or checking in generated `dist/` trees
- →When Make targets are expected to work without Nix for Nix-specific targets
- →When adding first-party extensions without updating the embedded manifest registry
Limitations
- →Cannot hand-edit or check in generated `dist/` trees
- →Make targets with `nix` in their name require Nix
- →Requires updating embedded manifest registry for first-party extensions
How it compares
This skill offers a specialized workflow for Fen repository maintenance, focusing on source-checkout development and efficient testing, unlike general development practices.
Compared to similar skills
fen-maintainer side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| fen-maintainer (this skill) | 0 | 3mo | Review | Advanced |
| command-development | 16 | 11mo | Review | Intermediate |
| skill-forge | 11 | 11mo | Review | Intermediate |
| codex-skill | 12 | 7mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
command-development
anthropics
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.
skill-forge
WilliamSaysX
Automated skill creation workshop with intelligent source detection, smart path management, and end-to-end workflow automation. This skill should be used when users want to create a new skill or convert external resources (GitHub repositories, online documentation, or local directories) into a skill. Automatically fetches, organizes, and packages skills with proactive cleanup management.
codex-skill
feiskyer
Use when user asks to leverage codex, gpt-5, or gpt-5.1 to implement something (usually implement a plan or feature designed by Claude). Provides non-interactive automation mode for hands-off task execution without approval prompts.
agent-factory
alirezarezvani
Claude Code agent generation system that creates custom agents and sub-agents with enhanced YAML frontmatter, tool access patterns, and MCP integration support following proven production patterns
subagent-driven-development
davila7
Use when executing implementation plans with independent tasks in the current session
peekaboo
openclaw
Capture and automate macOS UI with the Peekaboo CLI.