Verify a running backend endpoint actually works by calling it yourself, not by reading the code. When asked to "verify this endpoint", "test the API", "check the route works", "confirm the mutation persisted", "did the request succeed", or whenever a change adds or modifies an HTTP/RPC/GraphQL endpoint, identify the…
Audit CI/CD pipelines and agent integration points for injection, privilege escalation, secret exfiltration, and untrusted-input flows. When asked to "audit the CI pipeline", "review these GitHub Actions", "check the build for security", "is this workflow safe", "harden the deploy", or before shipping changes to CI…
Audit a project's dependencies and supply chain for risk. When asked to "audit dependencies", "check for vulnerable packages", "supply-chain audit", "scan for CVEs", "generate an SBOM", or before shipping/upgrading dependencies, scan the dependency graph for known CVEs, verify lockfile and pinned-version integrity…
Diagnose and fix a broken developer environment BEFORE work starts. When asked to "set up the dev environment", "why won't this build", "fix my environment", "the project won't run", "check my toolchain", "env doctor", "diagnose setup", or when a fresh clone / new machine / CI runner fails before any real task begins…
Produce bold, distinctive, accessible UI instead of generic AI-slop output. When asked to "design this screen", "build a UI", "make this look good", "style this component", "improve the design", "make it less generic", "pick colors and typography", "lay out this page", or when scaffolding any new frontend surface (web…
Turn a working diff into clean Conventional Commits, a well-structured pull request, and a changelog entry — WITHOUT ever committing on the user's behalf. When asked to "write a commit message", "commit this", "draft a PR", "open a pull request", "write the PR description", "squash these commits", "write a changelog…
Run a coding-interview practice session as the interviewer, and keep a permanent per-problem record of it. Use whenever the user pastes a coding problem (a LeetCode/NeetCode link, a problem statement, or a function signature), or says "interview me", "interview help", "learn help", "let's practice", "mock interview"…
The knowledge base is agentware's long-term memory across sessions. It does NOT live in this repo — it lives in an EXTERNAL directory the operator chose at onboarding. Resolve that directory at runtime.
Skill "onboarding" from r5rana/agentware, covering onboarding skill — agentware first-run flow, the core design (state this to the user), self-extension clause (always true), the steps and step 1 — welcome and explain.
Change data, schema, config, or file layout safely — with a backup and a tested rollback before you touch anything. When asked to "run this migration", "alter the schema", "add/drop a column", "migrate the database", "backfill this data", "rename this field", "change the data model", "move these files", "bulk update…
Apply security at design time, before code is written. When asked to "design this securely", "add a secure-by-design review", "what are the security requirements", "harden this feature", or when scoping any new endpoint, auth flow, data model, integration, or LLM/agent feature, walk a proactive checklist grounded in…
Scaffold a new spec-compliant, portable Agent Skill (folder + SKILL.md with YAML frontmatter where name == the folder, plus optional scripts/ and references/) and validate it against the agentskills.io standard. When asked to "create a skill", "scaffold a skill", "author a new skill", "make a SKILL.md", "turn this…
Security gate that vets any EXTERNAL skill, MCP server, or plugin BEFORE it is trusted or installed. When asked to "vet a skill", "review this MCP server", "is this plugin safe", "audit a downloaded skill", or before skill add installs anything, scan the SKILL.md / manifest for prompt-injection and…
Find the root cause of a bug methodically instead of guessing. When asked to "debug this", "why is this failing", "this test is flaky", "track down this crash", "find the root cause", "this worked before and now it doesn't", or when a fix attempt failed and you are tempted to try random changes, run a reproduce →…
Author and run focused, high-signal tests for code, the TDD way. When asked to "write tests", "add test coverage", "do TDD", "test this function", "cover this edge case", "get this to green", or when a change lands without tests, infer the project's existing test framework, write targeted tests for the changed or…
Enumerate threats at design time using STRIDE, data-flow diagrams, and trust-boundary analysis. When asked to "threat model this", "do a STRIDE analysis", "what could go wrong with this design", "map the attack surface", "find the trust boundaries", or when scoping a new system, integration, agent loop, or data flow…
Marking a UI task "complete" because the build and unit tests pass is risky — units don't catch routing bugs, hydration issues, race conditions on real network calls, broken visual states, or wrong API payloads. A real browser hitting the real running app is the only honest "complete" for a UI task. This skill is…