simplicityguy/agent-skills
A collection of agent skills: brand asset audits, comprehensive docs, READMEs, deep bug hunts, repo CI setup, and staff-level engineering.
Use when creating a new project's visual identity, auditing brand asset completeness, generating missing design deliverables, or when a project needs logos, favicons, OG images, or a design system document. Triggers on "brand assets", "design system", "favicon", "og image", "logo variants", "apple-touch-icon", "webmanifest".
Create and maintain a comprehensive end-user documentation suite in a docs/ directory — index page, categorized guides, consistent formatting, role-based navigation, and documentation standards. Use when setting up project docs from scratch or auditing/expanding existing docs.
Run a deep, multi-agent bug-hunt expedition over a whole codebase - one finder pass per bug-class lens, a different-model adversarial verifier that tries to refute every candidate, fingerprint plus judgment dedup against the issue tracker, and filing of only verified, non-duplicate defects, in operator-gated rounds. Use when the user asks for a bug hunt, bug sweep, "find bugs across the repo", a deep defect audit, or to resume or continue a previous hunt. Not for reviewing a single diff or PR, and not for fixing bugs.
Use when configuring Dependabot on a repo, checking an existing repo's Dependabot setup for problems, fixing red Dependabot PRs, or rolling the same Dependabot setup out across every repo an owner has. Triggers on "dependabot", "dependabot.yml", "dependabot labels", "dependabot secrets", "red dependabot PRs", "audit dependabot", "all repos".
Use when a SimplicityGuy GitHub repo setting (ruleset, label, merge method) was changed live and must be adopted into the homelab OpenTofu github module, or when regenerating the github inventory. Triggers on "adopt into homelab", "github-inventory", "desired-state.json", "owner.tftest.hcl", "github-state-reconcile".
Create or update a polished project README.md following a proven open-source structure — banner image, badge rows, centered nav bar, emoji-prefixed sections (What is, Architecture, Key Features, Quick Start, Documentation, Development, Technology Stack, Community, License, Acknowledgments), and "Made with" footer. Use when bootstrapping a new project's README, auditing an existing one for missing sections, or standardizing READMEs across projects. Triggers on "readme", "root readme", "project readme", "readme sections", "readme template".
Use when setting up or auditing GitHub repo automation - SHA-pinned GitHub Actions workflows, required status checks that block PRs, or Node 20 deprecation notices. Triggers on "required checks", "block PRs", "pin actions", "node20 deprecated", "branch ruleset".
Use when handling any non-trivial engineering request - features, migrations, performance, security fixes, refactors, "can we safely X" questions - or when the user says "sudo L7", "staff-level", or "L7 mode". Works like a staff engineer instead of a ticket-taker - it checks the premise, surfaces risks the request did not mention, pushes back when the ask is wrong, verifies the dangerous cases, and reports truthfully.