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 13 ore
49.409 skill-uri
- replay-user-flowsreticlehq/reticleTurn a user journey you just clicked through into a saved regression check that re-runs deterministically, with no model in the loop and no test code to write. Use when you have driven the same flow twice, when the user wants regression coverage without a Playwright suite, when a refactor needs proving against every existing journey, or when re-verifying by hand is costing a full drive every time.TestareFără avertismente★ 1,3 K↓ —
- requesting-code-reviewGanyuanRan/AegisUse when requesting independent code review, after implementation slices, before merging high-risk work, or when verification exposes evidence, baseline, architecture, compatibility, or retirement uncertainty.InginerieFără avertismente★ 1,4 K↓ —
- mariadb-operator-commentmariadb-operator/mariadb-operatorPost a comment (or a formal PR review) to a GitHub issue or pull request in mariadb-operator/mariadb-operator. Use whenever the user wants to publish something to GitHub for this repo — "comment on issue #123", "post this as a PR comment", "leave a note on #456", "reply on the PR" — and especially when they want the output of the mariadb-operator-pr-review skill delivered to GitHub instead of just shown in chat, e.g. "review PR #1234 and post it as a comment" or "post the review results to the PR". Always confirms the exact comment text with the user before publishing — never posts autonomously.InginerieFără avertismente★ 1 K↓ —
- learn-my-brandgooseworks-ai/goose-skillsLearn my brand once and stop asking me every time. Use when someone says learn my brand, set up my brand, here's our brand book, remember how we talk, what can we claim, can we say this, approve our claims, sign off our voice, our price or product changed, the client approved the claims, pick up where we left off, or check our claims are still current. Reads what GooseWorks already found about the brand, asks only the gaps as drafts to confirm, audits every claim (including ones research marked approved) and gets the ones that matter signed off with proof, scope and review date, turns the voice into rules the owner confirms, checks logo, colours and fonts, and saves it all as it goes so every other job loads it instead of asking. Ends with an unknowns list and a read-back. Not for who our customers are and what they say (use research-audience) or writing positioning from scratch (not covered yet).ȘtiințăFără avertismente★ 1,3 K↓ —
- hephaestus-buildagentlas-ai/Agentlas-OSUse when the user types /prompts:hep-build or /agentlas-build, mentions @Hephaestus for build work, asks to create a single Agentlas agent, create a multi-agent team, or package an existing local/external agent into Agentlas architecture.PlanificareFără avertismente★ 1,6 K↓ —
- agentlas-networkagentlas-ai/Agentlas-OSStaff a task from registered Local, owner Cloud, and public Hub agents.ProductivitateFără avertismente★ 1,6 K↓ —
- visual-contentkostja94/marketing-skillsWhen the user wants to plan, create, or repurpose visual content (images, infographics, social post images) across channels. Also use when the user mentions "content images," "social media images," "infographic," "visual content," "post image," "image specs," "visual repurposing," "content visuals," or "image for social post." For Pinterest, use pinterest-posts.MediaFără avertismente★ 1,1 K↓ —
- openspec-update-changeMemeMeow-Studio/MemeMeowUpdate an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.RedactareFără avertismente★ 1,3 K↓ —
- openspec-update-changeMemeMeow-Studio/MemeMeowUpdate an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.RedactareFără avertismente★ 1,3 K↓ —
- openspec-apply-changeMemeMeow-Studio/MemeMeowImplement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.ProductivitateFără avertismente★ 1,3 K↓ —
- openspec-archive-changeMemeMeow-Studio/MemeMeowArchive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.ProductivitateFără avertismente★ 1,3 K↓ —
- openspec-exploreMemeMeow-Studio/MemeMeowEnter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.FinanțeFără avertismente★ 1,3 K↓ —Apare și în 1 alt depozit
- openspec-apply-changeMemeMeow-Studio/MemeMeowImplement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.ProductivitateFără avertismente★ 1,3 K↓ —Apare și în 1 alt depozit
- 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↓ —
- cell-star-methodsbrycewang-stanford/Awesome-Journal-SkillsUse to build Cell's mandatory STAR Methods — the Key Resources Table, the three Resource Availability subsections, Experimental Model and Subject Details, Method Details, and Quantification and Statistical Analysis, in the exact required order.AlteleFără avertismente★ 1,4 K↓ —
- asplos-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ASPLOS campaign across the two-deadline cycle — sequencing evidence building, the September 9, 2026 submission gate, author-response windows, the December 21 notification, Major Revision resubmission six weeks later, artifact evaluation, and the April 2027 conference in Crete, with owners per risk.ProductivitateFără avertismente★ 1,4 K↓ —
- atc-review-processbrycewang-stanford/Awesome-Journal-SkillsUse when reasoning about how an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) submission is evaluated — the two-round extended-abstract model, the round-one gate by two reviewers, the round-two read by 3-4 reviewers, double-blind reviewing, rebuttal, conditional acceptance with shepherding, and how ATC differs from OSDI/SOSP/NSDI.InginerieFără avertismente★ 1,4 K↓ —
- cav-review-processbrycewang-stanford/Awesome-Journal-SkillsUse when reasoning about how a CAV (Computer Aided Verification) submission is evaluated, covering the two-stage reviewing process (two reviews then an early-reject filter, then two more reviews with a rebuttal), the partial double-anonymity by category, the accept/reject outcome, the optional non-conditional artifact evaluation, and how CAV differs from TACAS and FMCAD.InginerieFără avertismente★ 1,4 K↓ —
- ase-review-processbrycewang-stanford/Awesome-Journal-SkillsUse when reasoning about how an ASE (IEEE/ACM Automated Software Engineering) research submission is evaluated, covering double-anonymous review, the early-rejection stage before rebuttal, the Accept / Revision / Reject outcomes, the criteria-bound revision round, and how ASE's process differs from FSE's PACMSE Major Revision, ICSE's cycles, and ISSTA's rounds.InginerieFără avertismente★ 1,4 K↓ —
- vis-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when revising an IEEE VIS paper for a task-grounded visualization contribution on the first page, a design rationale that ties each visual encoding and interaction to a task, evaluation matched to the contribution type, honest limitations, and disciplined use of the VGTC/TVCG 9+2 page budget for a paper that will be read as an IEEE TVCG journal article.RedactareFără avertismente★ 1,4 K↓ —
- vldb-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the evaluation of a VLDB paper, covering workload and dataset realism at scale, competitor tuning fairness, scalability curves versus single points, tail-latency and throughput reporting, ablations that isolate the mechanism, and the loss-case disclosure PVLDB reviewers look for first.ȘtiințăFără avertismente★ 1,4 K↓ —
- wacv-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing WACV experiments, covering Applications-track systems evidence (latency, power, robustness under real constraints) versus Algorithms-track matched-baseline novelty, comparative assessment under the deployed condition, uncertainty over seeds and sessions, ablations, and evidence that survives the two-round review.DevOpsFără avertismente★ 1,4 K↓ —
- aaai-camera-readybrycewang-stanford/Awesome-Journal-SkillsUse when preparing an accepted AAAI paper for camera-ready source submission to AAAI Press, including proceedings page limits, two-column template compliance, copyright transfer, purchased extra technical pages, deanonymization, registration, oral or poster presentation, and final public artifact release.ȘtiințăFără avertismente★ 1,4 K↓ —
- aaai-related-workbrycewang-stanford/Awesome-Journal-SkillsUse when positioning an AAAI paper's novelty against archival work, contemporaneous arXiv or workshop papers, and AAAI/IJCAI/NeurIPS/ICML/ICLR neighbors across the broad AI scope, while staying inside AAAI's dual-submission and AI-as-source policy constraints and writing a related-work section legible to non-specialist reviewers.ȘtiințăFără avertismente★ 1,4 K↓ —
dac-submission
brycewang-stanford/Awesome-Journal-Skills
DesignActualizat 27 sept. 2026
De la autor
Use when auditing an ACM/IEEE Design Automation Conference (DAC) Research-Manuscript submission for Softconf readiness, covering the two-stage abstract-then-manuscript deadline, the 6+1-page ACM double-column page budget with its references-only last page, the double-blind anonymization sweep, TPC conflict-of-interest declaration, and desk-reject triage before the mid-to-late-November cutoff.
Instalare
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-submission -a claude-code
Se instalează în .claude/skills/dac-submission/ · 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ță: MIT
Verificări de siguranță pe SKILL.md
Niciun avertisment.
De ce 88
Securitate100
Proveniență77
Întreținere100
Licență100
Adopție50
Fișiere (1)
- SKILL.md