marcioaltoe/skills

A curated collection of agent skills for Claude Code and other compatible agents. Each skill is a focused set of instructions — frontmatter plus a SKILL.md body — that an agent loads on demand to extend its capabilities for a specific task.

Requirements

• Node.js 18+ (or Bun). The examples below use bunx; npx works the same way.
• A skills-aware agent (e.g. Claude Code).

Installation

Install via the skills CLI (published on npm).

# Install all skills globally
bunx skills add marcioaltoe/skills -g

# Install a specific category
bunx skills add marcioaltoe/skills/skills/git -g

# Install a single skill
bunx skills add marcioaltoe/skills/skills/git --skill commit-style -g

# List available skills without installing
bunx skills add marcioaltoe/skills --list

Without -g, skills are installed in the current project at .claude/skills/.

Categories

Category	Domain
ai/	Claude API, prompts, agents, skills (meta), MCPs
architecture/	DDD, modular decomposition, system design
backend/	APIs, databases, ORMs, auth, payments
business/	Strategy, ops, pricing, metrics, fundraising
copy/	Copywriting, pitch decks, brand storytelling
design/	UI/UX, interface design, landing pages
development/	TypeScript, Go, refactoring, general patterns
devops/	Docker, CI/CD, deploy, infra
frontend/	React, TanStack, Tailwind, shadcn, Storybook
git/	PRs, rebase, commits, git workflows
learning/	Meta-learning, retrospectives, action planning
marketing/	SEO, channels, outreach systems, brand identity
performance/	Core Web Vitals, Lighthouse, web perf
security/	Threat modeling, security audits, ownership maps
testing/	Vitest, Playwright, QA, anti-patterns
tools/	Obsidian, file formats, diagrams, auxiliary MCPs
writing/	Docs, READMEs, communication

Documentation skills

Two evidence-first documentation skills generate one selected Markdown document at a time instead of creating a full docs set by default:

• backend-docs: document backend architecture, bounded contexts, onboarding, API contracts, or backend gaps.

  --mode <architecture|onboarding|gap-analysis|api-contracts|bounded-context> --backendPath <path-or-scope> [--outputPath <doc.md>]
  

• frontend-docs: document frontend architecture, onboarding, route/data contracts, component systems, DESIGN.md compliance, or UI gaps.

  --mode <architecture|onboarding|gap-analysis|route-data|component-system> --frontendPath <path-or-scope> [--outputPath <doc.md>]
  

Install examples:

bunx skills add marcioaltoe/skills/skills/backend/backend-docs --skill backend-docs -g
bunx skills add marcioaltoe/skills/skills/frontend/frontend-docs --skill frontend-docs -g

Anatomy of a skill

Each skill lives at skills/<category>/<skill-name>/SKILL.md and starts with YAML frontmatter the CLI uses to discover and route it:

---
name: commit-style
description: Creates commit messages following Conventional Commits — use when the user asks "commit", "git commit", or after changes are ready to be recorded.
metadata:
  category: git
  tags: [git, commits, conventional-commits]
  version: 0.1.0
  author: marcioaltoe
---

# Commit Style

Short paragraph explaining the skill's purpose.

## When to use

- Scenario 1
- Scenario 2

## How to apply

Concrete, imperative steps the agent will follow literally.

The description is the most important field — agents read it to decide whether to load the skill. See AGENTS.md for full conventions.

Contributing

Contributions are welcome.

1. Fork the repo and create a branch.
2. Add your skill under the appropriate skills/<category>/ folder (see AGENTS.md for the structure and frontmatter contract).
3. Test locally: bunx skills add ./skills/<category>/<your-skill> -g.
4. Format before committing: make fmt (uses oxfmt — Markdown, JS, TS, JSON).
5. Commit using Conventional Commits — e.g. feat(development): add my-skill.
6. Open a pull request.

CI runs npx skills add . --list on every PR to validate frontmatter. If it fails, double-check name, description, and YAML indentation.

License

MIT — see LICENSE.