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 18 ore
49.492 de skill-uri
- api-test-planmohitagw15856/pm-claude-skillsPlan tests for an API endpoint or service — functional, negative, and contract. Use when asked to test an API, write API test cases, plan REST/GraphQL endpoint testing, or validate an API contract. Produces an API test plan — per-endpoint cases (status codes, schema, auth, validation, errors), boundary/negative cases, contract checks, and non-functional notes — so the API is verified beyond the happy 200.TestareFără avertismente★ 1,5 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↓ —
- 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↓ —
- 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↓ —
- asc-workflowrorkai/app-store-connect-cli-skillsDefine, validate, run, resume, and audit repo-local multi-step automations with current `asc workflow` and `.asc/workflow.json`, including step outputs and safe release/TestFlight workflows.ProductivitateFără avertismente★ 1,1 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↓ —
- wsdm-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the evaluation of a WSDM paper - offline ranking and recommendation metrics with bias controls, temporal-split protocols for interaction logs, baseline selection from recent WSDM/SIGIR/KDD editions, ablations that isolate the mechanism, efficiency reporting, and online-evidence framing.ȘtiințăFără avertismente★ 1,4 K↓ —
- codex-exechashgraph-online/awesome-codex-pluginsRun one prompt through headless Codex and capture the result. Use when: wanting a one-shot `codex exec` run or CI step. Not for batches or retries.AlteleFără avertismente★ 1,5 K↓ —Apare și în 2 alte depozite
- vis-supplementarybrycewang-stanford/Awesome-Journal-SkillsUse when deciding what belongs in an IEEE VIS paper body versus its supplemental materials, covering the VGTC/TVCG 9+2 page budget, the supplemental video that VIS reviewers routinely watch, the one-week supplemental deadline extension, double-blind supplemental anonymization, and how to split a visualization paper between the reviewed pages and the archive.MediaFără avertismente★ 1,4 K↓ —
- socc-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing ACM SoCC evaluations, covering real or realistic deployments over simulation, production or representative workloads and traces, tail-latency and cost as first-class metrics, fair tuned baselines, scale and multi-tenancy behavior, reproducible measurement pipelines, and matching evidence to the shape of each cloud claim.DevOpsFără avertismente★ 1,4 K↓ —
- stoc-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when judging whether computation belongs in a STOC (ACM Symposium on Theory of Computing) paper at all — STOC accepts on theorems, with no empirical-evaluation expectation — and when it does, scoping it as certified proof computation, constructive search, or clearly labeled illustration rather than benchmarking.MediaFără avertismente★ 1,4 K↓ —
- pods-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the analytical "evidence" of an ACM PODS paper — worst-case and average-case analyses, matching upper and lower bounds, dichotomy completeness, correct complexity assumptions, and the occasional empirical validation when a theory paper claims practicality — matching the rigor to the shape of each theoretical claim.ȘtiințăFără avertismente★ 1,4 K↓ —
- popl-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing the empirical component of a POPL paper — deciding whether evidence should be a mechanization, a prototype, case studies, or benchmarks; reporting proof effort and case-study coverage honestly; and keeping performance numbers in a supporting role so the formal claim stays the paper's center of gravity.ȘtiințăFără avertismente★ 1,4 K↓ —
- category-page-generatorkostja94/marketing-skillsDeprecated compatibility entry for Commerce Category Page construction. This page is now maintained in Pagina; install and use page-builder to build a new Commerce Category Page.AlteleFără avertismente★ 1,1 K↓ —
- pldi-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing a PLDI evaluation — choosing defensible benchmark suites and baseline compiler configurations, measuring runtime, compile time, and memory with warmup and variance discipline, running ablations that isolate the claimed mechanism, and scoping claims to the platforms measured.ProductivitateFără avertismente★ 1,4 K↓ —
- version-releasehoangsonww/Claude-Code-Agent-MonitorChoose and apply the correct semantic version bump for this repository. Use for every user-visible release, before merge when a change set should ship as patch, minor, or major, and whenever package/plugin/desktop version metadata must stay synchronized.AlteleFără avertismente★ 1,1 K↓ —
- push-to-forked-prhoangsonww/Claude-Code-Agent-MonitorPush the current working tree directly to a GitHub PR whose head lives on a **fork**, without creating a new branch and without pushing to `origin` (which is usually the upstream). Invoke when the user says things like "push straight to PRAlteleFără avertismente★ 1,1 K↓ —Apare și în 2 alte depozite
- local-seokostja94/marketing-skillsWhen the user wants to optimize for local search, set up Google Business Profile, or build local citations. Also use when the user mentions "local SEO," "Google Business Profile," "Google Maps," "NAP," "citations," "local search," "local business," or "service area." For location pages, use programmatic-seo.MarketingFără avertismente★ 1,1 K↓ —
- kdd-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when revising a KDD paper into the venue's register, where the first page names a data regime, a mechanism, and scale evidence, efficiency adjectives trace to design decisions, and two-column sigconf pages punish sprawl. Covers Research vs ADS voice, dataset-size discipline, assertive contribution bullets, and 8-page compression.RedactareFără avertismente★ 1,4 K↓ —
- fixing-flaky-testsamplifthq/openmeldGuides an agent through reproducing, root-causing, fixing, and validating flaky tests in the PostHog monorepo. Use when a test fails intermittently in CI but passes on rerun or locally, when `hogli ci:insights` or the debugging-ci-failures skill classifies a failure as a flaky test, when given a GitHub Actions URL for a flaky job, when asked to check Trunk Flaky Tests for a test, PR, or master, or when asked to deflake, stabilize, or fix a flaky Jest, pytest, or Playwright test. Core discipline: reproduce locally before changing anything, fix the root cause (never mask it with sleeps, retries, or bigger timeouts), and prove the fix with an N-run validation loop sized to the observed failure rate. Stabilizing is not the only valid outcome — the skill also gates whether the test should exist, so deleting a test that catches nothing real, or re-leveling one that flakes because of the level it runs at, are first-class endings.TestareFără avertismente★ 1,4 K↓ —
- ipsn-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing IPSN-lineage evaluations, covering real testbeds and deployments, ground-truth instrumentation, energy/latency/footprint measurement on real hardware, on-device/TinyML profiling, estimation-theoretic baselines and bounds, and matching evidence to the shape of each sensing claim across the IP and SPOTS tracks.DevOpsFără avertismente★ 1,4 K↓ —
oma-pm
first-fluke/oh-my-agent
PlanificareActualizat alaltăieri
De la autor
Product manager that decomposes requirements into actionable tasks with priorities and dependencies. Use for planning, requirements, specification, scope, prioritization, task breakdown, and ISO 21500, ISO 31000, or ISO 38500-aligned planning recommendations.
Instalare
npx skills add first-fluke/oh-my-agent --skill oma-pm -a claude-code
Se instalează în .claude/skills/oma-pm/ · 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ță78
Întreținere100
Licență100
Adopție51
Fișiere (7)
- SKILL.md
- resources/error-playbook.md
- resources/examples.md
- resources/execution-protocol.md
- resources/iso-planning.md
- resources/plan-phase-protocol.md
- resources/task-template.json