Browse Secure Claude Skills
Search verified agent skills and review security grades before installing · full A–Z index
- Engineering ArchitectureApply persistent engineering and architectural principles to every task. Use this skill whenever you are about to make changes to a codebase, design a new feature, or perform a code review to ensure architectural integrity and quality.Votes: 0GitHub stars: 8
- SdlcRun the full software development lifecycle pipeline, from issue creation through implementation, documentation, and learnings capture.Votes: 0GitHub stars: 10
- Threat ModelSTRIDE threat modeling with CAPEC drill-down and DREAD-lite scoring. Builds a DFD from lode/ domain knowledge, identifies threats per trust boundary, maps to concrete attack patterns, and produces a prioritized threat register.Votes: 0GitHub stars: 2
- Tech Debt AuditTech debt and architecture audit for .NET repos. Produces plans/TECH_DEBT_AUDIT.md with file-cited findings, severity, and effort estimates. Supports module scoping and focused-mode shortcuts (crap, dead-code, duplicates, suppressions, solid) for single-dimension audits. Does not auto-invoke. Triggers on: tech debt audit, debt audit, codebase health check, architecture review, code quality assessment, audit tech debt, tech debt scan, code health, crap analysis, crap score, dead code audit, fi...Votes: 0GitHub stars: 2
- Strategy AuditStrategic alignment audit for codebases. Applies Roger Martin's strategy framework directly to code, analyzing what the code reveals about its strategic choices, investment levels, and capability reinforcement. Produces a prioritized findings report and feeds actionable refactorings into dev-planning. Use for code review through a strategy lens, feature gap analysis, investment mismatch detection, or surfacing undocumented strategic choices. Triggers on: strategy audit, strategic audit, strat...Votes: 0GitHub stars: 2
- ReviewUnified code review: --local (diff review), --pr (adversarial PR review), --apply (batch fixes from last review).Votes: 0GitHub stars: 2
- Review LocalOrchestrated code review of git diff using parallel agents. Standard mode (diff-scoped) or full mode (adds Roslyn semantic analysis). Produces severity-grouped plan.Votes: 0GitHub stars: 2
- Bash PatternsWrite, review, and fix Bash (.sh) scripts using project conventions and best practices. Always use this skill when writing any .sh file, creating a new shell script, fixing a bash error or runtime error, reviewing shell code, adding a new script to scripts/, or when the user asks about bash style, naming, formatting, or patterns. This skill combines official style rules with project-specific patterns to produce correct, portable scripts on the first try. Trigger on: write bash, create .sh, ba...Votes: 0GitHub stars: 2
- Learn From Code ReviewsCollect the code review feedback you received on your own pull requests and distill it into durable, cited rules to consult before design and implementation work so the same mistakes stop recurring. Use when the user says /learn-from-code-reviews, "learn from my code reviews", "learn from my PR reviews", "what do reviewers keep telling me", "turn review feedback into rules", "why do I keep getting the same review comments", "review my feedback history", or wants a review-rules checklist to ap...Votes: 0GitHub stars: 10
- Robust FirstSurvive first. Be correct later.Votes: 0GitHub stars: 56
- Mooco MirrorParallel introspection for MOOCO sessions and cross-orchestrator comparisonVotes: 0GitHub stars: 56
- MarkdownPlain text formatting that's readable raw AND renderedVotes: 0GitHub stars: 56
- Github> Talk is cheap. Show me the code.Votes: 0GitHub stars: 56
- Code ReviewSystematic code analysis with evidence collectionVotes: 0GitHub stars: 56
- Architecture CoopDesign or redesign an architecture with the user by working through key decisions together.Votes: 0GitHub stars: 4
- Google Engineering CultureGoogle-grade software engineering culture encompassing Code Readability, Design Doc Review, Blameless Postmortem, Testing Philosophy, Code Review standards, and engineering excellence practices distilled from Google's internal engineering culture documented in "Software Engineering at Google" and real Google/Brain/DeepMind experience. USE WHEN: establishing engineering standards, reviewing code quality, designing development workflows, onboarding engineers, setting code review guidelines, ad...Votes: 0GitHub stars: 2
- Competitive RadarTracks competitors weekly across 6 signals: pricing page diffs, homepage positioning changes, blog/RSS posts, job postings (hiring as strategy signal), GitHub star velocity and releases, and daily critical-change alerts for pricing or funding keywords. Delivers a structured digest to Slack, Telegram, WhatsApp, or Discord every Monday. Fires same-day alerts for critical changes. Use when asked to "add competitor", "track competitor", "competitor digest", "what changed at [company]", "competito...Votes: 0GitHub stars: 2
- Agent Team OrchestrationOrchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team of 2+ agents with different specializations, (2) Defining task routing and lifecycle (inbox → spec → build → review → done), (3) Creating handoff protocols between agents, (4) Establishing review and quality gates, (5) Managing async communication and artifact sharing between agents.Votes: 0GitHub stars: 2
- Gemini PromptingInternal guidance for composing Gemini 2.5 Pro/Flash prompts for coding, review, diagnosis, and research tasks inside the Gemini Claude Code pluginVotes: 0GitHub stars: 47
- Golang SafetyDefensive Golang coding to prevent panics, silent data corruption, and subtle runtime bugs. Use when encountering nil panics, append aliasing, map concurrent access, float comparison pitfalls, or zero-value design questions. Also use when reviewing code for nil-safety, numeric conversion overflow, resource lifecycle issues (defer in loops), or defensive copying of slices and maps.Votes: 0GitHub stars: 8