Updated 6d ago
by helderberto
agent-skills
Helder Berto's 🛠️ Battle-tested software engineering skills for AI coding agents 🤖
20 GitHub stars (20)
+4 in 30 days
| Period | New stars |
|---|---|
| Oct 1 | 0 |
| Oct 2 | 0 |
| Oct 3 | 0 |
| Oct 4 | 0 |
| Oct 5 | 0 |
| Oct 6 | 0 |
| Oct 7 | 0 |
| Oct 8 | 0 |
| Oct 9 | 0 |
| Oct 10 | 0 |
| Oct 11 | 0 |
| Oct 12 | +1 |
| Oct 13 | 0 |
| Oct 14 | 0 |
| Oct 15 | 0 |
| Oct 16 | 0 |
| Oct 17 | 0 |
| Oct 18 | 0 |
| Oct 19 | 0 |
| Oct 20 | 0 |
| Oct 21 | 0 |
| Oct 22 | 0 |
| Oct 23 | 0 |
| Oct 24 | 0 |
| Oct 25 | +1 |
| Oct 26 | +1 |
| Oct 27 | 0 |
| Oct 28 | 0 |
| Oct 29 | 0 |
| Oct 30 | 0 |
| Oct 31 | 0 |
| Nov 1 | 0 |
| Nov 2 | +1 |
- 30 skills (30 skills found in its SKILL.md files)
- 2 forks (2 forks)
- 6d ago last update (Last updated 6d ago)
Install
Skills CLI
npx skills add helderberto/agent-skills
Asks which skills and agents to install. Just one: npx skills add helderberto/agent-skills --skill a11y-audit — add -g for every project.
Claude Code
git clone https://github.com/helderberto/agent-skillscp -r "agent-skills/skills/a11y-audit" ~/.claude/skills/
Copies the a11y-audit skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add helderberto/agent-skills
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md — showing the first 30 of 38 files.
-
a11y-audit
Audit accessibility (WCAG) in frontend code. Use when asked to "check accessibility", "audit a11y", "check WCAG", or find accessibility issues. Don't use for backend code, bundle size (/perf-audit), or translations (/i18n).
skills/a11y-audit/SKILL.md on GitHub (opens in a new tab) -
architecture-audit
Surface architectural friction across a codebase and propose refactors toward deep modules as RFCs. Use when asked to audit architecture, find structural friction, or spot refactor opportunities. Don't use for one module's interface (/codebase-design) or a diff (/code-review).
skills/architecture-audit/SKILL.md on GitHub (opens in a new tab) -
build
Implement the next unblocked phase of a plan with feedback loops, mark its checkboxes, offer a commit. Use after /plan when `.specs/plans/<slug>.md` exists, or when asked to build the next phase. Don't use for unplanned changes (/tdd) or to check progress (/test).
skills/build/SKILL.md on GitHub (opens in a new tab) -
code-review
Review a GitHub PR for bugs, security, performance, and code quality. Use when asked to review a PR or give pull request feedback. Don't use for local uncommitted changes, creating PRs, or merging.
skills/code-review/SKILL.md on GitHub (opens in a new tab) -
codebase-design
Shared vocabulary for designing deep modules. Use when designing or improving a module's interface, placing a seam, making code more testable, or when another skill needs it. Don't use for codebase-wide audits (/architecture-audit) or UI components (/frontend-ui-engineering).
skills/codebase-design/SKILL.md on GitHub (opens in a new tab) -
commit
Group unstaged changes into atomic commits by concern, matching repository style. Use when asked to "commit", "create a commit", or "commit changes". Don't use for pushing (/ship) or pull requests.
skills/commit/SKILL.md on GitHub (opens in a new tab) -
create-adr
Record an Architecture Decision Record (ADR) — 1–3 sentences on what was decided and why. Use when user says "create an ADR", "record this decision", or just made an architecturally significant choice. Don't use for forward-looking specs (/spec) or repo conventions (CLAUDE.md).
skills/create-adr/SKILL.md on GitHub (opens in a new tab) -
create-pull-request
Create a GitHub pull request — concise body on the repo's PR template, conventional-commit title, ticket refs. `--draft` for a draft PR, `--diagram[=type]` to add a mermaid diagram of the change.
skills/create-pull-request/SKILL.md on GitHub (opens in a new tab) -
create-skill
Create or restructure agent skills — frontmatter, description routing, progressive disclosure. Use when asked to create, write, or build a new skill, or "make a skill for X". Don't use for eval-driven trigger optimization (skill-creator) or one-off prose edits to a skill.
skills/create-skill/SKILL.md on GitHub (opens in a new tab) -
deps-audit
Check dependencies for known vulnerabilities and staleness. Use when asked to "audit dependencies", "check for vulnerabilities", or check dependency health. Don't use for code quality review.
skills/deps-audit/SKILL.md on GitHub (opens in a new tab) -
diagnose
Disciplined diagnosis loop for hard bugs and performance regressions. Use when user says "diagnose" or "debug this", or reports something broken, throwing, failing, or slow. Don't use to build a feature or fix an understood bug test-first (/tdd).
skills/diagnose/SKILL.md on GitHub (opens in a new tab) -
domain-modeling
Build a project's domain model — challenge terms, pin down a ubiquitous language, write the glossary down. Use when defining domain terminology, resolving ambiguous terms, or another skill needs the shared vocabulary. Don't use for a single architectural decision (/create-adr) or explaining code (/explain-code).
skills/domain-modeling/SKILL.md on GitHub (opens in a new tab) -
e2e
Write end-to-end tests for user flows with the project's E2E framework (Playwright, Cypress, other). Use when asked to "write e2e tests", "add Playwright/Cypress tests", or test a user flow end-to-end. Don't use for unit or component tests (/tdd) or manual browser checks (/visual-validate).
skills/e2e/SKILL.md on GitHub (opens in a new tab) -
explain-code
Explain code with visual diagrams and analogies. Use when explaining how code works, walking through a codebase area, or the user asks "how does this work?" Don't use for modifying code, fixing bugs, or multi-session learning (/teach).
skills/explain-code/SKILL.md on GitHub (opens in a new tab) -
fortify
Improve existing code without changing behavior — split large functions, backfill tests, simplify. Use when asked to "fortify", "make robust", "bulletproof", "strengthen", "add missing tests", "split functions", "simplify", "clean up", or "reduce complexity". Don't use for new features (/tdd), security (/harden), or PR review.
skills/fortify/SKILL.md on GitHub (opens in a new tab) -
frontend-ui-engineering
Front-load UI construction decisions — component boundary and prop API, state placement, required states, responsiveness, accessibility. Use when creating or refactoring a component, page, or design-system primitive. Don't use for pure logic (/tdd), throwaway exploration (/prototype), or auditing finished UI (/a11y-audit).
skills/frontend-ui-engineering/SKILL.md on GitHub (opens in a new tab) -
grill-me
Relentless interview to sharpen a plan or design. Use when the user wants to stress-test a plan, pressure-test assumptions, or says "grill me" or "poke holes in this". Don't use for code review (/code-review) or gathering initial requirements (/spec).
skills/grill-me/SKILL.md on GitHub (opens in a new tab) -
handoff
Compact the current conversation into a handoff document for another agent. Use when the user wants to hand off, move context to a fresh session, or says "write a handoff". Don't use to summarize for the current session or to brief on plan progress (/test).
skills/handoff/SKILL.md on GitHub (opens in a new tab) -
harden
Harden code where untrusted input enters the system. Use when implementing auth, handling user input, storing sensitive data, integrating external APIs, adding file uploads, or crossing any trust boundary. Don't use for secret scanning (/safe-repo) or dependency CVEs (/deps-audit).
skills/harden/SKILL.md on GitHub (opens in a new tab) -
i18n
Audit internationalization coverage and find hardcoded strings. Use when asked to "check i18n", "find hardcoded strings", or verify translation coverage. Don't use for backend code, projects without an i18n library, accessibility (/a11y-audit), or bundle size (/perf-audit).
skills/i18n/SKILL.md on GitHub (opens in a new tab) -
perf-audit
Audit frontend bundle size and performance. Use when asked to "audit performance", "analyze bundle", "check bundle size", or find frontend bottlenecks. Don't use for backend performance, database queries, or projects without a frontend build step.
skills/perf-audit/SKILL.md on GitHub (opens in a new tab) -
plan
Turn a spec into a multi-phase implementation plan of tracer-bullet vertical slices. Use after /spec when `.specs/specs/<slug>.md` exists, or when asked to break work into phases or slices. Don't use without a spec, or for single-file changes with obvious scope.
skills/plan/SKILL.md on GitHub (opens in a new tab) -
prose-fix
Fix prose formatting, typos, and clarity in markdown or text files. Use when asked to "fix dashes", "fix typos", "clean up text", or "improve sentences". Don't use for code style, linting, or full rewrites (/revise).
skills/prose-fix/SKILL.md on GitHub (opens in a new tab) -
prototype
Build a throwaway prototype — a terminal app for state/logic questions, or several UI variations toggleable from one route. Use when comparing design directions before committing, or the user says "prototype", "mock up", "try a few approaches". Don't use for production code (/build, /tdd).
skills/prototype/SKILL.md on GitHub (opens in a new tab) -
research
Investigate a question against primary sources and capture cited findings as Markdown. Use when the user wants a topic researched, docs or API facts gathered, or reading delegated to a background agent. Don't use for implementing against pinned dependency versions (/source-driven) or codebase search.
skills/research/SKILL.md on GitHub (opens in a new tab) -
review
Fan out parallel read-only reviewers over a diff and consolidate into one severity-ranked verdict. Use for a full pre-ship review, "review/validate this PR", or "spawn agents to review". Don't use for a single-lens PR review (/code-review), one audit, or triaging existing comments (/triage-review).
skills/review/SKILL.md on GitHub (opens in a new tab) -
revise
Structurally edit article drafts — reorder sections, tighten arguments, improve clarity. Use when asked to "revise", "improve my article", or "edit my draft". Don't use for typos or formatting (/prose-fix), code docs, or non-article content.
skills/revise/SKILL.md on GitHub (opens in a new tab) -
safe-repo
Check the repository for sensitive data. Use when asked to "check for sensitive data" or verify no credentials or company data are committed; `--diff` scopes to staged + unstaged changes. Don't use for general code review or non-git directories.
skills/safe-repo/SKILL.md on GitHub (opens in a new tab) -
ship
Commit and push changes with a pre-launch gate (validate-code + safe-repo) by default. `--fast` skips the gate.
skills/ship/SKILL.md on GitHub (opens in a new tab) -
source-driven
Implement features from official docs for the exact installed dependency versions, not training data. Use when asked to "check the docs", "use official docs", "source-driven", or with unfamiliar APIs/libraries. Don't use for well-known stdlib APIs or project-internal code.
skills/source-driven/SKILL.md on GitHub (opens in a new tab)
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.