Menu
SkillsMP has collected 17 skills from axross/claude-loop-template. Open a skill to review its source and details.
Showing 17 of 17 collected skills.
Creating, refining, splitting, consolidating, renaming, or auditing an agent skill — the authoring rules for the agentskills.io format, and the validators that enforce them. Triggers on drafting a `SKILL.md`, editing frontmatter, tightening a `description`,…
Deciding whether material belongs in a skill at all or in the project's own documentation, and then which tier it lives in — the storage, install, and drift model for a project keeping skills in two tiers. Triggers on adding, editing, renaming, moving, or…
Writing or reviewing code that handles untrusted input, secrets, outbound requests, rendered content, or third-party dependencies — the OWASP Top 10:2025 lens in two modes, writing secure-by-default code and judging the risk a change introduces. Triggers on…
Writing, refactoring, or reviewing code for maintainability or design — keeping what you change readable, cohesive, and cheap to change next time. Triggers on "readable", "too long", "refactor", "abstraction", "cohesion", "magic number", "dead code", "what…
Reviewing a code change — a pull request, a branch or commit-range diff, or a post-implementation self-review of your own work before calling it done. The methodology for judging whether a change already written is safe to merge, and for reporting why. Not…
Authoring or revising a Git commit message, titling a pull request, or judging whether a header conforms — the Conventional Commits v1.0.0 header contract, plus a validator that catches a malformed header before it reaches your history. Triggers on "write a…
Writing, reviewing, refactoring, or running end-to-end tests, or verifying a change through the e2e suite — whole-system checks that drive a running build the way a real user or client does. Triggers on snapshots, test IDs, selectors or locators, polling and…
Reading or writing GitHub from inside an agent session that shares one connected operator identity — any issue, pull request, comment, label, review, or branch operation, not only end-to-end change loops. The operating model that keeps those writes safe and…
Updating a project's own documentation when a change alters what it says, and reading it before planning one — the `docs/` tree recording what the project is and how it works now, and the mechanism that corrects it when a change makes it wrong. Triggers on…
Driving a code change or document update end-to-end through the plan → code → review loop — "deliver this issue", "implement and open a PR for X", a free-form change request, or resuming an in-progress run. The project's default change loop, carrying one unit…
Writing, refining, or reviewing a PRD, feature spec, plan document, RFC, design doc, or issue description — the canonical tool-agnostic section structure such a document takes, and the craft behind each section. Includes the plan-writing or issue-drafting…
Handling what you do not know, and handing back what you found — the conduct baseline underneath whatever else a session is doing, applying to a question answered in one turn as fully as to a feature built over many. Triggers on any uncertainty about facts,…
Reviewing whether a change carries adequate verification evidence — "is this verified", "did this break anything", "were the required checks run". The reviewer's QA pass on top of the development verification rules, judging the evidence a change offers rather…
Every task that touches a project — implementing, refactoring, running a project command, or writing a pull request body. The baseline discipline underneath the specialised skills — keep the change scoped, run the format and lint loop, map what the change…
Deciding what a system should report about itself, independent of the SDK that carries it out — the vendor-neutral layer over logs, metrics, traces, error handling, and product events. Triggers on code that logs, throws, catches, reports an error, tracks an…
Drafting, structuring, editing, or reviewing a technical document — a design doc, RFC, ADR, runbook, README, API reference, changelog, or post-mortem — and the sentence-level craft that makes any of them readable. Triggers on "make this clearer", "how should…
Writing, refactoring, reviewing, or running unit tests — fast, isolated checks that exercise one small exported contract from the caller's point of view. Triggers on mocks and fakes, fixtures, schema and codec tests, snapshot choices, coverage questions,…