最高评分
社区最喜爱的高星技能，质量有保障。
wandb-reporting
marin-community
Publish W&B runs, reports, or artifacts only when explicitly requested or required for a requested experiment's dense numeric results.
write-design-doc
marin-community
Create Marin design-doc artifacts only when explicitly asked for a design doc, one-pager, or proposal; do not use for inline architecture discussion.
write-tests
marin-community
Add, revise, or review Marin tests for an explicit behavior change, regression, or test-quality request.
writing-style
marin-community
Apply Marin house style when producing or revising commit, pull-request, issue, comment, documentation, report, or blog prose.
background-research
marin-community
Perform an explicitly requested prior-work search for a Marin research, design, or experiment decision and produce a cited brief.
skill-parallel-agents
nyldn
Multi-tentacled orchestration using Double Diamond methodology. Use when: PRIORITY TRIGGERS (always invoke immediately):. "/octo:multi" (explicit command). "run this with all providers", "run with all providers"
skill-deck
nyldn
Generate slide decks from briefs with optional multi-AI research. Use when: AUTOMATICALLY ACTIVATE when user requests:. "create a deck", "build slides", "make a presentation". "generate a pitch deck", "create board presentation"
skill-security-framing
nyldn
URL validation and content wrapping for untrusted sources. Use when: This skill provides SECURITY UTILITIES - it should be referenced by other skills,. not invoked directly by users. Auto-integrate when:. Fetching content from URLs
noslop
marin-community
Deslop, simplify, or review low-value tests and prose only when explicitly requested for a branch or diff.
design-critique
Owl-Listener
Facilitate a structured team critique — framing, feedback rules, and actionable outcomes. Use when running a session with people in the room. For a solo expert review, use heuristic-evaluation (prototyping-testing).
design-debt-audit
Owl-Listener
Inventory and prioritise accumulated design inconsistencies across a product. Use when drift has built up over time. For token coverage specifically use design-token-audit (designer-toolkit); for WCAG gaps use accessibility-audit (design-systems).
onboard
wesammustafa
Explains this repository's shared Claude Code setup to a new teammate, covering what is committed and shared, what stays personal, and what the team-kit plugin adds. Use when someone asks how the team's Claude Code setup works or what they get by cloning the repository.
onboard
wesammustafa
Claude Code guide in three levels, Beginner to Advanced: hands-on lessons with checked exercises, every volatile fact cited to its source. Independent community guide.
onboard
wesammustafa
Explains the team's shared Claude Code setup
five-whys
wesammustafa
Finds the root cause of a bug, failure or recurring problem by asking "why" until the answer is a cause you can fix. Use when the user asks why something keeps happening, or wants the root cause rather than a quick fix.
tdd
wesammustafa
TODO
five-whys
wesammustafa
Claude Code guide in three levels, Beginner to Advanced: hands-on lessons with checked exercises, every volatile fact cited to its source. Independent community guide.
Claude-Code-Everything-You-Need-to-Know
wesammustafa
Find the root cause of a bug by asking why five times
CLAUDE.md Review
wesammustafa
Audit a CLAUDE.md file for the patterns that actually degrade Claude Code's output — vagueness, unnamed files, stale facts, and bloat. Use when asked to review, audit, improve, shrink, or fix a CLAUDE.md, and when a project's results feel inconsistent or Claude keeps rediscovering the same context.
wordpress-penetration-testing
zebbern
This skill should be used when the user asks to "pentest WordPress sites", "scan WordPress for vulnerabilities", "enumerate WordPress users, themes, or plugins", "exploit WordPress vulnerabilities", or "use WPScan". It provides comprehensive WordPress security assessment methodologies.
deep-module-refactor
zebbern
Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.
r3f-best-practices
zebbern
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.
project-sizing-guide
zebbern
"Software project effort estimation assistant. Outputs three-point estimates (optimistic/most-likely/pessimistic values with confidence intervals), T-shirt sizes, or Function Point Analysis (FPA) counts. Triggered when users ask 'how long will this feature take,' need to assess project workload, perform PERT estimation, T-shirt sizing, FPA, sprint planning, or quote-based effort breakdowns."
secure-code-review
zebbern
"Systematically reviews code for SQL injection, XSS, SSRF, broken access control, cryptographic failures, and other common OWASP Top 10 vulnerabilities, providing vulnerable code examples and ready-to-use remediation guidance. Trigger this skill when users ask for a security review, vulnerability scan, or penetration testing assistance, or mention keywords like OWASP, SQL injection, XSS, code audit, or security checklist."