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 12 ore
49.409 skill-uri
- 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↓ —
- regression-alerthoangsonww/Claude-Code-Agent-MonitorCompare this period's reliability against the prior period using Agent Monitor data — error rate (APIError/total) and tool-failure rate (PreToolUse→PostToolUse gap) — flag any regression where reliability got worse, and optionally wire a persistent alert rule so the dashboard catches the next regression automatically. Use when checking whether reliability degraded.AlteleFără avertismente★ 1,1 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↓ —
- cost-alerthoangsonww/Claude-Code-Agent-MonitorReview the configured cost alert rules and the alerts currently fired on the Agent Monitor dashboard, then explain exactly what tripped and why. Uses /api/alerts (fired feed) and /api/alerts/rules (definitions). Use when checking spend alerts or asking why a cost alarm went off.InginerieFără avertismente★ 1,1 K↓ —
- session-debughoangsonww/Claude-Code-Agent-MonitorDebug a specific session by inspecting its full event chain (PreToolUse, PostToolUse, Stop, SubagentStop, Compaction, APIError, TurnDuration, Notification events), agent hierarchy (recursive parent/child tree with subagent_type and depth), token usage with compaction baselines, workflow intelligence data (orchestration DAG, error propagation by depth), and session metadata (thinking_blocks, turn_count, total_turn_duration_ms).InginerieFără avertismente★ 1,1 K↓ —
- design-systemdaveebbelaar/bamaAccent color and design system for a macOS app, from the app's accent and the accent picker in Settings to Swift tokens in code plus a design/DESIGN-SYSTEM.md that says which token to use when. Use when the user wants a brand or accent color, wants people to pick a color, when an app has more than a few screens, when screens drift apart or animations feel inconsistent, or when the user asks for themes, a style guide, or design tokens.DesignFără avertismente★ 1,5 K↓ —
- model-mixhoangsonww/Claude-Code-Agent-MonitorBreak down Claude Code usage by model family (Opus / Sonnet / Haiku) from the Agent Monitor dashboard — each family's share of tokens, share of cost, and the spots where an expensive model is doing cheap work. Pulls per-model token and cost splits from /api/pricing/cost, current rates from /api/pricing, fleet token totals from /api/analytics, and per-session model assignment from /api/sessions. Use when deciding model routing or whether to downshift work to a cheaper tier.DateFără avertismente★ 1,1 K↓ —
- hook-diagnosticshoangsonww/Claude-Code-Agent-MonitorDiagnose Claude Code hook installation, delivery, and ingestion issues. Checks hook configuration, connectivity, event flow, and identifies common problems. Use when events are not appearing in the dashboard.InginerieFără avertismente★ 1,1 K↓ —
- daily-journalhuytieu/COG-second-brainA passive daily work journal that Claude keeps FOR you so you never have to write it yourself. Append short entries after meaningful work (what was done, what you focused on, artifacts touched) to 01-daily/journal/YYYY-MM-DD.md. Run a guided reflection at night or in the morning. Use when you run /daily-journal, say "log this to my journal", "add to today's journal", "reflect on today/yesterday", or when finishing a meaningful chunk of work in any session.RedactareFără avertismente★ 1,3 K↓ —Apare și în 1 alt depozit
- openqodexopenqodex/openqodexCode review for the current change, before it is pushed. One command runs the security, secret, dependency and lint scanners that fit the changed files, a separate reviewer that checks every scanner finding and is given every changed line, and prints a short receipt with the path of the full report. Use before every git push, when asked for a code review, a security scan, or to review changes, a diff or a pull request, and when a push was blocked or warned by OpenQodex.SecuritateFără avertismente★ 1,1 K↓ —Apare și în 2 alte depozite
- dag-maphoangsonww/Claude-Code-Agent-MonitorRender the multi-agent orchestration DAG for a session — parent→child subagent edges, tree depth, and fan-out — from the Agent Monitor workflow intelligence API. Cross-checks the orchestration dataset against the raw agent records and session detail. Use when visualizing how a session's agent structure was organized.MediaFără avertismente★ 1,1 K↓ —
- hri-workflowbrycewang-stanford/Awesome-Journal-SkillsUse to plan an ACM/IEEE HRI campaign backward from the full-paper deadline through the abstract-then-paper two-step, the rebuttal, the program-committee meeting, camera-ready, and the March conference, coordinating the parallel alt.HRI, Late-Breaking Reports, video, and Student Design deadlines.ProductivitateFără avertismente★ 1,4 K↓ —
- error-scanhoangsonww/Claude-Code-Agent-MonitorScan recent Claude Code activity for errors and failure signals across all sessions using Agent Monitor data — APIError events and PreToolUse→PostToolUse gaps (tools that started but never completed) — then group failures by tool and model and rank them by frequency. Use when checking for errors or asking "what's failing right now".InginerieFără avertismente★ 1,1 K↓ —
- run-historyhoangsonww/Claude-Code-Agent-MonitorInspect CCAM dashboard-run history and relate live run handles to persisted Claude Code or Codex sessions. Use when finding a prior launched task, checking whether a run is still attached, reviewing start/end status, or deciding whether to resume, view, or relaunch work.InginerieFără avertismente★ 1,1 K↓ —
- run-agenthoangsonww/Claude-Code-Agent-MonitorLaunch and supervise Claude Code or Codex through the CCAM Run API. Use when the user wants to start a monitored agent, select a model, approval policy, sandbox, or working directory, send a follow-up, inspect live output, resume a native session, or stop a dashboard-launched run.InginerieFără avertismente★ 1,1 K↓ —
- 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↓ —
- sosp-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the evaluation of a SOSP paper — mapping every claim to an experiment, choosing baselines a systems PC will accept as fair, mixing microbenchmarks with end-to-end and failure runs, reporting tails and overheads honestly, and isolating the mechanism the design credits.DesignFă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↓ —
- write-skillsdzhng/skillsCreate or revise agent skills. Use when adding a new skill file, renaming a skill, simplifying an existing skill, improving trigger descriptions, or deciding what belongs in a skill versus references, scripts, assets, or ordinary docs.RedactareFără avertismente★ 1,4 K↓ —
- close-specdzhng/skillsWhen a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).PlanificareFără avertismente★ 1,4 K↓ —
- marketing-contextalirezarezvani/claude-skillsUse at the start of any marketing project, or when ICP, positioning or brand voice are missing, before other marketing skills. Writes the shared context file the other skills read and validates it with context_validator.py.MarketingFără avertismente★ 29,2 K↓ —
- reviewdzhng/skillsCloseout pass on a finished substantive change — sequence refactor-clean (shape), code-review (diff), and write-docs (docs) so all three run, in the order where each feeds the next. Use after implementing a slice or feature and before calling it done or committing; when the user asks for a final review, a cleanup-and-document pass, or to "review everything." For a diff-only audit, reach code-review directly.InginerieFără avertismente★ 1,4 K↓ —
- eval-skillsdzhng/skillsEval and improve a skill against golden cases — run the target skill blind in a fresh, context-free subagent on each example input, grade the artifact against the expected outcome, and let the gaps drive the edits. Use when the user wants to test/eval/improve/harden a skill, says "this skill keeps producing X / keeps missing Y", or hands a skill plus example input→expected-output pairs. Pairs with [write-skills](../write-skills/SKILL.md) (the authoring principles every fix obeys).TestareFără avertismente★ 1,4 K↓ —
- human-gatealirezarezvani/claude-skillsUse before shipping anything that needs human sign-off (a plan, spec, report, page, migration or irreversible action). Builds a review page with review_page_builder.py and runs human_gate.py, which refuses to close with an open blocker or no named reviewer.PlanificareFără avertismente★ 29,2 K↓ —
laravel-tdd
hashgraph-online/awesome-codex-plugins
TestareActualizat ieri
De la autor
Test-driven development for Laravel with PHPUnit and Pest, factories, database testing, fakes, and coverage targets.
Instalare
npx skills add hashgraph-online/awesome-codex-plugins --skill laravel-tdd -a claude-code
Se instalează în .claude/skills/laravel-tdd/ · 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ță78
Întreținere100
Licență100
Adopție51
Fișiere (1)
- SKILL.md