br4zz4:commons-craft

Creates, updates, and renames shared skills and commands in a provider-neutral commons directory.

Updated May 25, 2025
One-click install
npx skills add https://github.com/oporpino/commons --skill br4zz4-commons-craft-oporpino
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: br4zz4:commons-craft
Source: https://github.com/oporpino/commons/tree/main/ai/shared/skills/br4zz4%3Acommons-craft
Command: npx skills add https://github.com/oporpino/commons --skill br4zz4-commons-craft-oporpino

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams repeatedly solve the same problems in isolated projects, and reusable knowledge stays locked in one codebase. This Skill standardizes how shared skills and commands are created, named, and distributed across all projects via a single commons plugin. ## Core Features & Use Cases - Skill and command scaffolding: Creates commons skills under ai/shared/skills/<name>/SKILL.md and commands under ai/shared/commands/<name>/, enforcing naming conventions where the directory name governs the loaded name. - Distribution safety rules: Prevents the symlink-inside-plugin-root failure that silently breaks claude plugin install, and defines the reinstall-and-verify workflow for Claude and Codex providers. - Project vs commons split: Guides when knowledge belongs in shared commons versus project-local .project/ai/skills/, including the generic-script-plus-thin-wrapper pattern for shell tasks. - Use Case: A developer notices a Makefile target reused across three projects and asks to turn it into a shared skill; the Skill creates the correctly named directory, frontmatter, and commit in .commons. ## Quick Start Ask the AI to create a new commons skill named deploy-check that validates environment configuration before running deployments.

Frequently Asked Questions about br4zz4:commons-craft

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a shared skill for Claude and Codex?▼

Create `ai/shared/skills/<name>/SKILL.md` with a bare directory name and matching `name:` frontmatter, then reinstall the plugin with `claude plugin uninstall` and `claude plugin install` so the cache picks it up. Both providers read the same canonical files from `ai/shared/`.

How do I decide between a commons skill and a project skill?▼

Ask whether the pattern would make sense in any project regardless of stack or domain. If yes, it belongs in commons under `ai/shared/skills/`; project-specific logic, credentials, or single-project workarounds go in `.project/ai/skills/` instead.

Why did my skills disappear after reinstalling the Claude plugin?▼

Claude's plugin installer copies the plugin tree without following symlinks, so symlinked `skills/` directories inside the plugin root are silently skipped. The fix is keeping real directories in `ai/shared/` and never symlinking into the plugin root.

What naming rules apply to skill directories?▼

The directory name governs the loaded skill name, not the frontmatter `name:` field. Never put a prefix like `br4zz4:` in the directory name, keep descriptions at 60 characters or less, and write content in English starting with a TLDR line.

When should a shell script be moved to commons?▼

Generalize a script only when a second project would reuse it. Move the generic mechanism to `.commons/shell/tasks/<domain>/<name>.sh` with all project specifics passed as flags, and keep a thin local wrapper that calls it with the app's values.