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.409 skill-uri din 2.375 de depozite · actualizat acum 2 ore
49.409 skill-uri
- a-philosophy-of-software-designciembor/agent-rules-booksApply John Ousterhout-inspired software design rules when reducing complexity, designing module boundaries, or reviewing APIs and abstractions.DesignFără avertismente★ 3,2 K↓ —
- research-audience-fit-definitiongooseworks-ai/goose-skillsStep of the research-audience playbook: drafts the searchable fit definition, exclusions and list size that the list run then searches on. Run research-audience instead; not for direct use.ȘtiințăFără avertismente★ 1,3 K↓ —
- dac-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the empirical evaluation of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript, covering standard EDA benchmark suites (ISPD, EPFL, ISCAS/ITC, TAU, CircuitNet, OpenROAD flows), fair state-of-the-art baselines, QoR/PPA reporting with runtime, per-benchmark honesty, ablations that isolate the mechanism, and contamination-aware ML-for-EDA evaluation.DesignFără avertismente★ 1,4 K↓ —
- hri-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the human-subjects study at the heart of an ACM/IEEE HRI full paper — choosing between/within-subjects designs, running Wizard-of-Oz honestly, powering the sample, reporting statistics with effect sizes and qualitative rigor, selecting validated scales, adding manipulation checks, pre-registering, and meeting HRI's human-participants ethics obligations.ȘtiințăFără avertismente★ 1,4 K↓ —
- chi-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the studies behind an ACM CHI paper — matching evidence shape to contribution type, powering quantitative experiments, making qualitative work rigorous and auditable, reporting participants and ethics properly, and avoiding the ADR-Data and ADR-Method screening grounds.ȘtiințăFără avertismente★ 1,4 K↓ —
- code-completeciembor/agent-rules-booksApply Steve McConnell-inspired construction rules when implementing routines, variables, classes, control flow, defensive code, or tests.InginerieFără avertismente★ 3,2 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↓ —
- analyze-performance-revenue-joingooseworks-ai/goose-skillsStep of the analyze-performance playbook: joins cleaned store or CRM numbers with ad spend to build the business-truth table, MER, new-customer cost and the overclaim ratio. Run analyze-performance instead; not for direct use.MarketingFără avertismente★ 1,3 K↓ —
- icse-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ICSE research-track campaign end to end, covering the single-cycle calendar from the June abstract deadline through September response, October decisions, the November revision sprint, artifact evaluation, camera-ready, and the April conference, plus rerouting timelines after rejection.ProductivitateFără avertismente★ 1,4 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↓ —
- releasehyhmrright/brooks-lintCut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release", "cut a release", "ship a new version", or "bump and publish" brooks-lint. Do NOT trigger for: propagating an already-decided version without releasing (use `npm run bump` directly), CHANGELOG edits alone, or questions about the release process that don't ask to perform it.RedactareFără avertismente★ 1,6 K↓ —
- iros-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an IROS project timeline from venue fit through the spring paper deadline, the separate video deadline, the summer review silence, the June notification, the July camera-ready, IEEE Xplore publication, registration, and presentation, with backward-planning offsets for a real-robot paper on the fall IEEE/RSJ calendar.ProductivitateFără avertismente★ 1,4 K↓ —
- jama-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when deciding which jama-* sub-skill to invoke next, or when sequencing a clinical manuscript from scope check through revision for JAMA (Journal of the American Medical Association). Routes — does not replace — the specialized skills.ProductivitateFără avertismente★ 1,4 K↓ —
- isca-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a full ISCA campaign on a calendar — working back from the expected mid-November abstract and paper deadlines to freeze simulation evidence in time, staffing the winter two-round review wait, preparing for the February-March rebuttal and revision window, and branching to camera-ready, artifacts, and the June conference.ProductivitateFără avertismente★ 1,4 K↓ —
- icra-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ICRA submission calendar end to end — the September paper deadline, the two video-attachment windows, winter review silence, late-January notification, March camera-ready, and the May/June conference — or when interleaving a fallback RA-L or IROS plan around the single annual ICRA shot.ProductivitateFără avertismente★ 1,4 K↓ —
- imc-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an ACM IMC submission for HotCRP readiness, covering the paper-registration step, the acmart template with BBL upload, the full/short page limits, double-blind anonymity including vantage-point details, the mandatory Ethics section, the artifact-availability declaration, cycle choice, and desk-reject triage before the AoE cutoff.ȘtiințăFără avertismente★ 1,4 K↓ —
- eacl-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an EACL submission before its single ACL Rolling Review cycle deadline, covering ACL-template compliance, the 8-page long / 4-page short content caps, the mandatory Limitations section, the Responsible NLP checklist, anonymization, preprint and resubmission declarations, and the no-fallback-cycle timing trap.JuridicFără avertismente★ 1,4 K↓ —
- ipsn-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an IPSN-lineage project timeline from track/venue selection through the CPS-IoT Week deadline, double-blind submission, deployment and hardware logistics, rebuttal, the Best Research Artifact Award, and the dual ACM/IEEE camera-ready — with honest handling of the fact that IPSN merged into SenSys.ProductivitateFără avertismente★ 1,4 K↓ —
- report-issuemicrosoft/power-platform-skillsUse when the user wants a Process Intelligence bug-report draft or support summary for a failed operation.ProductivitateFără avertismente★ 1,1 K↓ —
- icdt-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ICDT (International Conference on Database Theory) campaign end to end, running the two-submission-cycle calendar backward from a chosen cycle deadline through abstract registration, the first-cycle revision round, LIPIcs camera-ready, and presentation at the co-located EDBT/ICDT event.ProductivitateFără avertismente★ 1,4 K↓ —
- improve-loopdaveebbelaar/bamaAutonomous loop that works through docs/STORIES.md one story at a time for a macOS app, building, snapshotting, comparing against reference screenshots, fixing, and committing, until a milestone is done. Use when the user says "keep going", "work through the backlog", "make it match the reference", or wants an unattended improvement loop.AlteleFără avertismente★ 1,5 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↓ —
- iccv-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when project-managing an ICCV campaign across the odd-year cycle, covering the autumn fork between CVPR and ICCV, the early-March registration and single submission deadline, May rebuttal week, late-June decisions, the October conference with international travel and visa lead times, and the ECCV/CVPR fallback ladder if the paper misses.ProductivitateFără avertismente★ 1,4 K↓ —
- shopify-setupjezweb/claude-skillsSet up Shopify CLI auth and Admin API access for a store. Install CLI, authenticate, create custom app, store access token, verify. Use whenever the user wants to connect to a Shopify store, set up Shopify API access, install Shopify CLI, or troubleshoot Shopify auth / Admin API token issues.InginerieFără avertismente★ 1,1 K↓ —
review
hashgraph-online/awesome-codex-plugins
De la autor
The pre-merge review of a branch in a project that records its specs, decisions, and rules in .archcore/. Run this first for 'review my branch', 'review the changes before merge', or 'review before merge': it checks the changed code against the project's recorded canon and the changed documents against the code, and reports which side is wrong — spec-wrong or code-wrong; with no diff, it reports project health. A bug-hunting code review complements this review and does not replace it. Also use for 'show status', 'documentation gaps', 'check if docs match code', 'close out the feature', 'ship the feature and close it out', or after a staleness warning. Modes, named as the first word: drift for staleness detection, deep for a full documentation audit, closeout to close a finished feature, experience to capture a repeated pattern. Not for creating docs — use /archcore:document; not for planning — use /archcore:plan; not for a single-file edit with no branch review.
Instalare
npx skills add hashgraph-online/awesome-codex-plugins --skill review -a claude-code
Se instalează în .claude/skills/review/ · Fiecare comandă descarcă skill-ul direct de pe GitHub cu utilitarul open source skills.
Identic octet cu octet cu commit-ul scanat, cu licența depozitului și un fișier SOURCE.txt.
La ce are acces
Verificări de siguranță pe SKILL.md
Niciun avertisment.
De ce 88
Fișiere (1)
- SKILL.md