Skill-uri pentru agenți pe care le poți verifica înainte să le instalezi
Skill-uri SKILL.md publice din depozite GitHub cu peste 50 de stele și de la producători, scanate și evaluate. Instalează oricare dintre ele cu o singură comandă în Claude Code, Cursor, Codex, GitHub Copilot sau Gemini CLI.
49.492 de skill-uri din 2.391 de depozite · actualizat acum 12 ore
49.492 de skill-uri
- doctorhashgraph-online/awesome-codex-pluginsRead-only docflow diagnosis: scans docs, config, changelog, and links, then recommends init, adopt, or repair. Use when asked "check docs setup", "should I set up docflow", "why is docflow not working", or "doctor".AlteleFără avertismente★ 1,5 K↓ —
- new-skillhyhmrright/brooks-lintScaffold a new brooks-lint analysis skill so it passes `npm run validate` and `npm run evals` on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends paired eval scenarios. Triggers when the maintainer asks to "add a new skill", "scaffold a skill", or "create a brooks-lint mode". Do NOT trigger for: editing an existing skill's content, adding a single eval to an existing skill, or authoring skills for some other plugin.RedactareFără avertismente★ 1,6 K↓ —
- catch-upNouhashgraph-online/awesome-codex-pluginsBrief the user in plain language on what happened in this conversation since their last typed message, with pictures where they help, then lay out every decision waiting on them with a recommendation, evidence and risk. Use when the user runs /catch-up.AlteleFără avertismente★ 1,5 K↓ —
- new-skillhyhmrright/brooks-lintScaffold a new brooks-lint analysis skill so it passes `npm run validate` and `npm run evals` on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends paired eval scenarios. Triggers when the maintainer asks to "add a new skill", "scaffold a skill", or "create a brooks-lint mode". Do NOT trigger for: editing an existing skill's content, adding a single eval to an existing skill, or authoring skills for some other plugin.RedactareFără avertismente★ 1,6 K↓ —
- routerhashgraph-online/awesome-codex-pluginsFind the right doc before reading code. Use when asked "where is X documented", "is there a spec/ADR for X", "what's the roadmap", "open bugs", "read the docs about X", or "share the docs".PlanificareFără avertismente★ 1,5 K↓ —
- brooks-harnesshyhmrright/brooks-lintMaintenance orchestrator for the brooks-lint plugin itself. Runs a sequential subagent pipeline — author → eval → QA → trigger-audit → release — to add or edit a skill, refresh the eval suite, keep the four manifests + all README translations + CHANGELOG + AGENTS/GEMINI in sync, audit trigger boundaries, and cut releases. Drives the five agents in .codex/agents/ (skill-author, eval-curator, consistency-qa, trigger-boundary-auditor, release-manager). Triggers when the maintainer asks to work ON brooks-lint itself: "add a new skill", "edit the brooks-debt guide", "update the eval suite", "fix the trigger descriptions", "make this change and validate it", "release brooks-lint", "bump and publish", and follow-ups: "re-run", "re-validate", "update that skill", "redo the audit", "do the X part again". Do NOT trigger for: USING the brooks-lint analysis skills on some target codebase (that's brooks-review / brooks-audit / brooks-debt / brooks-test / brooks-health / brooks-sweep); generic questions about brooks-lint tTestareFără avertismente★ 1,6 K↓ —
- brooks-harnesshyhmrright/brooks-lintMaintenance orchestrator for the brooks-lint plugin itself. Runs a sequential subagent pipeline — author → eval → QA → trigger-audit → release — to add or edit a skill, refresh the eval suite, keep the four manifests + all README translations + CHANGELOG + AGENTS/GEMINI in sync, audit trigger boundaries, and cut releases. Drives the five agents in .claude/agents/ (skill-author, eval-curator, consistency-qa, trigger-boundary-auditor, release-manager). Triggers when the maintainer asks to work ON brooks-lint itself: "add a new skill", "edit the brooks-debt guide", "update the eval suite", "fix the trigger descriptions", "make this change and validate it", "release brooks-lint", "bump and publish", and follow-ups: "re-run", "re-validate", "update that skill", "redo the audit", "do the X part again". Do NOT trigger for: USING the brooks-lint analysis skills on some target codebase (that's brooks-review / brooks-audit / brooks-debt / brooks-test / brooks-health / brooks-sweep); generic questions about brooks-lint TestareFără avertismente★ 1,6 K↓ —
- using-aegisGanyuanRan/AegisUse when starting a turn or checking Aegis skill routing.AlteleFără avertismente★ 1,4 K↓ —
- ui-ux-governanceGanyuanRan/AegisUse when designing, changing, or reviewing user-facing interfaces or interaction flows, including API changes that alter visible states or recovery. Backend-only work without user-facing effects stays on its existing route.DesignFără avertismente★ 1,4 K↓ —
- discount-marketing-strategykostja94/marketing-skillsWhen the user wants to plan, implement, or optimize discount and promotional pricing strategy. Also use when the user mentions "discount strategy," "promo code," "coupon," "redeem code," "lifetime deal," "LTD," "AppSumo," "Black Friday," "Cyber Monday," "BFCM," "seasonal sale," or "promotional pricing." For pricing page, use pricing-page-generator.MarketingFără avertismente★ 1,1 K↓ —
- receiving-code-reviewGanyuanRan/AegisUse when receiving code review feedback before implementing suggestions, especially when feedback is unclear, risky, disputed, or technically questionable.InginerieFără avertismente★ 1,4 K↓ —
- communicating-conciselyGanyuanRan/AegisUse when the user asks for caveman mode, fewer tokens, brief responses, compressed communication, or otherwise explicitly requests a much shorter answer.AlteleFără avertismente★ 1,4 K↓ —
- domain-architecturekostja94/marketing-skillsWhen the user wants to decide domain structure for multiple products or brands—subfolder vs subdomain vs independent domain. Also use when the user mentions "subfolder vs subdomain," "subdirectory vs subdomain," "multiple products domain," "multiple websites," "brand architecture," "branded house," "house of brands," "where to host product," "domain structure," or "hub-spoke domain." For brand SERP, use multi-domain-brand-seo.PlanificareFără avertismente★ 1,1 K↓ —
- test-driven-developmentGanyuanRan/AegisUse when the user explicitly requests strict or test-first TDD, or when the current conversation already contains an explicit `TDD Route: strict` decision from another Aegis workflow.TestareFără avertismente★ 1,4 K↓ —
- subagent-driven-developmentGanyuanRan/AegisUse when executing a written implementation plan with independent tasks in the current session where delegation beats inline coordination cost; otherwise inline. Ad-hoc 2+ tasks without a plan use dispatching-parallel-agents.MarketingFără avertismente★ 1,4 K↓ —
- domain-selectionkostja94/marketing-skillsWhen the user wants to choose an SEO-friendly domain for a new site—brand vs keyword domain, TLD selection, or domain best practices. Also use when the user mentions "domain choice," "pick domain," "SEO-friendly domain," "brand domain," "EMD," "PMD," "exact match domain," "partial match domain," "TLD," ".ai domain," ".com vs .io," "domain length," "domain history," or "defensive domain registration." For migration, use rebranding-strategy.MarketingFără avertismente★ 1,1 K↓ —
- establishing-project-contextGanyuanRan/AegisUse when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.ProductivitateFără avertismente★ 1,4 K↓ —
- verification-before-completionGanyuanRan/AegisUse when about to claim work is complete, fixed, passing, verified, release-ready, or ready to commit, merge, publish, or hand off.InginerieFără avertismente★ 1,4 K↓ —
- brooks-reviewhyhmrright/brooks-lintPR code review that surfaces decay risks, design smells, and maintainability issues with concrete Symptom → Source → Consequence → Remedy findings, drawing on twelve classic engineering books. Triggers when: user asks to review code, check a PR, shares a diff or pastes code asking "does this look right?" / "any issues here?" / "ready to merge?", or asks for feedback on a function, class, or file. Also triggers when user mentions: code smells / refactoring / clean architecture / DDD / SOLID principles / Hyrum's Law / deep modules / tactical programming / conceptual integrity / Brooks's Law / Mythical Man-Month / second system effect. Do NOT trigger for: questions about how to write code from scratch, language syntax questions, or framework/tool questions where no existing code is shared.InginerieFără avertismente★ 1,6 K↓ —
- brooks-debthyhmrright/brooks-lintTech debt assessment that identifies, classifies, and prioritizes maintainability problems — helping teams build a refactoring roadmap — drawing on twelve classic engineering books. Triggers when: user asks about tech debt, refactoring priorities, what to clean up first, or asks "why is this so hard to change?", "what should we fix first?", or "how do I justify refactoring to management?". Do NOT trigger for: server health checks, HTTP /health endpoints, Kubernetes probes, database health, or application uptime — "health" in those contexts is infrastructure, not code quality. Also not for single-function refactoring questions.DevOpsFără avertismente★ 1,6 K↓ —
- brooks-testhyhmrright/brooks-lintTest quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow execution, poor readability. Triggers when: user asks about test quality, shares test files for review, or expresses frustration: "tests keep breaking whenever I change anything", "our tests take forever", "tests pass but bugs still reach production", or "we have too many mocks". Do NOT trigger for: writing new tests from scratch (use the regular test-writing workflow) or testing framework/syntax questions — this skill reviews an existing suite for structural quality problems, not individual test authoring.TestareFără avertismente★ 1,6 K↓ —
- distribution-channelskostja94/marketing-skillsWhen the user wants to plan product distribution via marketplaces, app stores, or third-party platforms. Also use when the user mentions "distribution channels," "marketplace listing," "app store listing," "Figma plugin," "Chrome extension marketplace," "AWS Marketplace," "Shopify app," "GPTs store," "app distribution," or "third-party marketplace." For channel mix, use integrated-marketing.DevOpsFără avertismente★ 1,1 K↓ —
- affiliate-marketingkostja94/marketing-skillsWhen the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.MarketingFără avertismente★ 1,1 K↓ —
- brooks-audithyhmrright/brooks-lintArchitecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books. Triggers when: user asks to audit architecture, review folder/module structure, check for circular imports, understand how the codebase is organized, or asks "does this follow clean architecture?" or "why does everything depend on everything?". Also triggers for onboarding requests: "explain this codebase to a new developer" or "give me a codebase tour" (use onboarding mode). Do NOT trigger for: PR-level code review (use brooks-review) or line-level refactoring questions — this skill analyzes structural/module-level concerns, not individual functions.PlanificareFără avertismente★ 1,6 K↓ —
openship-config
fcakyon/claude-codex-settings
DevOpsActualizat acum 20 de ore
De la autor
This skill should be used when the user asks to "create openship.json", "configure an OpenShip deployment", "make a repo deployable on OpenShip", or fix "openship config validate" errors.
Instalare
npx skills add fcakyon/claude-codex-settings --skill openship-config -a claude-code
Se instalează în .claude/skills/openship-config/ · Fiecare comandă descarcă skill-ul direct de pe GitHub cu utilitarul open source skills.
Descarcă .zip
Identic octet cu octet cu commit-ul scanat, cu licența depozitului și un fișier SOURCE.txt.
La ce are acces
Doar instrucțiuniNu am văzut acces la rețeaLicență: APACHE-2.0
Verificări de siguranță pe SKILL.md
Niciun avertisment.
De ce 88
Securitate100
Proveniență77
Întreținere100
Licență100
Adopție50
Fișiere (8)
- LICENSE
- SKILL.md
- references/compose-multi-service.mdx
- references/environment-variables.mdx
- references/fields.md
- references/openship-json.mdx
- references/openship.schema.json
- references/upstream.json