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.418 skill-uri din 2.407 depozite · actualizat acum 17 minute
49.416 skill-uri
- building-livekit-agentsfcakyon/claude-codex-settingsBuilds voice and chat AI agents with LiveKit Agents on LiveKit Cloud or a self-hosted server. Use when the user asks to "build a voice agent", "create a LiveKit agent", "add voice AI to my app", "implement handoffs", "structure an agent workflow", "my agent is slow / too chatty", "it says it booked but nothing was saved", "make it confirm before committing", "it keeps re-asking things the caller already said", or is writing code against the LiveKit Agents SDK. Covers architecture: designing for latency, keeping context small, splitting a monolithic agent into handoffs and tasks, and designing for voice. Also covers keeping the model in charge of meaning while code owns state, approvals, and effects. For API specifics use reading-livekit-docs. To check behavior use debugging-livekit-agents and testing-livekit-agents.TestareFără avertismente★ 1,2 K↓ —
- fizz-convertpashov/skillsConvert English-language properties in PROPERTIES.md (produced by the Fizz skill) into Solidity assertions inside the existing fuzz harness, then flip their checkboxes. Trigger on "fizz-convert", "convert properties", "implement properties from PROPERTIES.md", "convert PROPERTIES.md to Solidity".AlteleFără avertismente★ 1,3 K↓ —
- planning-with-filesOthmanAdi/planning-with-filesPersistent file-based planning for multi-step AI-agent work. Keeps task_plan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and emits aggregate counts only; --replay may emit bounded nonce-framed excerpts. Optional gated mode can request continuation only when the host supports it and never runs commands declared in Markdown. The skill has no network upload path. Use for research or work needing 5+ tool calls.PlanificareFără avertismente★ 27,9 K↓ —Apare și în 1 alt depozit
- colt-related-workbrycewang-stanford/Awesome-Journal-SkillsUse when positioning a COLT (Conference on Learning Theory) submission against prior bounds and models — building the known-versus-new comparison across COLT/ALT lineage, STOC/FOCS, NeurIPS-and-ICML theory tracks, statistics journals, and arXiv concurrency, while respecting anonymity and the parallel-submission rules.ȘtiințăFără avertismente★ 1,4 K↓ —
- conext-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ACM CoNEXT campaign backward from a deadline, covering the choice between the December and June submission cycles, the mandatory registration step, the one-shot major-revision window, the reproducibility badge opt-in due at submission, PACMNET camera-ready, and presentation — all on CoNEXT's distinctive two-cycles-per-year calendar.ProductivitateFără avertismente★ 1,4 K↓ —
- colt-camera-readybrycewang-stanford/Awesome-Journal-SkillsUse when converting an accepted COLT (Conference on Learning Theory) paper into its PMLR proceedings version, covering de-anonymization, acknowledgements and funding restoration, appendix consolidation into the archival PDF, PMLR volume metadata and BibTeX hygiene, rebuttal-promised edits, and presentation logistics.DocumenteFără avertismente★ 1,4 K↓ —
- cikm-related-workbrycewang-stanford/Awesome-Journal-SkillsUse when positioning a CIKM submission against three literatures at once — retrieval, mining, and knowledge management/databases — building the boundary-work paragraph, guarding against misattributing SIGIR/KDD/ICDM classics to CIKM, and handling preprints under the arXiv-declaration and dual-submission rules.ȘtiințăFără avertismente★ 1,4 K↓ —
- colm-camera-readybrycewang-stanford/Awesome-Journal-SkillsUse when converting a COLM acceptance into the final paper — the August 7 camera-ready deadline in 2026, de-anonymization and the one-page acknowledgments allowance, folding rebuttal commitments into the text, publishing on OpenReview, releasing artifacts publicly, and planning the October conference in San Francisco.ȘtiințăFără avertismente★ 1,4 K↓ —
- colm-related-workbrycewang-stanford/Awesome-Journal-SkillsUse when positioning a COLM paper inside the fastest-moving literature in ML — triaging arXiv-heavy citations, handling concurrent work fairly, citing model and dataset artifacts correctly, distinguishing COLM's three-edition archive from adjacent venues' archives, and keeping self-citation double-blind safe.ȘtiințăFără avertismente★ 1,4 K↓ —
- icml-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an ICML main-track submission for OpenReview, LaTeX formatting, 8-page body, anonymity, supplementary material, impact statement, dual submission, concurrent ICML submissions, reciprocal reviewing, and LLM/prompt-injection policy compliance.JuridicFără avertismente★ 1,4 K↓ —
- iclr-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an ICLR main-conference submission for OpenReview readiness, double-blind anonymity, page limits, reciprocal reviewing, LLM-use disclosure, dual-submission policy, supplementary material, and desk-reject risk.AlteleFără avertismente★ 1,4 K↓ —
- ijcai-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an IJCAI or IJCAI-ECAI project timeline from venue fit through abstract registration, full-paper upload, author information, PPI payment, summary-reject risk, author response, notification, camera-ready, in-person presentation, and artifact release.ProductivitateFără avertismente★ 1,4 K↓ —
- icsme-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an IEEE ICSME project timeline from venue and track choice through abstract registration, paper submission, the early-decision cut and author-response rebuttal, notification, IEEE Xplore camera-ready, the ROSE-Festival artifact evaluation, and presentation, with backward-planning offsets for a maintenance/evolution paper and honest handling of the single-annual-round calendar.ProductivitateFără avertismente★ 1,4 K↓ —
- dashboard-statushoangsonww/Claude-Code-Agent-MonitorQuick dashboard health and status overview — checks the Agent Monitor API (port 4820), reports session/agent/event counts from /api/stats, confirms WebSocket connectivity, reads the redacted hook status returned by /api/settings/info, and shows data freshness (last event timestamp). Use to verify the monitoring system is operational.InginerieFără avertismente★ 1,1 K↓ —
- imc-related-workbrycewang-stanford/Awesome-Journal-SkillsUse when writing or auditing the related-work and positioning of an ACM IMC paper, covering the measurement literature lanes, positioning against prior datasets and vantage points, delta-first framing, citing the datasets and tools you build on, distinguishing IMC from SIGCOMM/NSDI/PAM prior art, and keeping self-citations double-blind.ȘtiințăFără avertismente★ 1,4 K↓ —
- icse-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an ICSE research-track submission for HotCRP readiness, covering the mandatory abstract deadline, the 10-page-plus-2-reference-page IEEE format, double-anonymous rules, the open-science Data Availability section, supplementary uploads, and desk-reject triage before the AoE cutoff.ȘtiințăFără avertismente★ 1,4 K↓ —
- icra-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an ICRA paper for upload — PaperPlaza account and metadata, the 6-page-plus-2-reference-page limit, IEEE two-column template compliance, the double-anonymous rule introduced in the 2026 cycle, video-attachment specs (180 s, 20 MB), dual-submission conflicts with RA-L, and return-without-review triggers.MediaFără avertismente★ 1,4 K↓ —
- hri-camera-readybrycewang-stanford/Awesome-Journal-SkillsUse when preparing the camera-ready of an accepted ACM/IEEE HRI paper — de-anonymizing systematically, completing ACM+IEEE dual-publication metadata (CCS concepts, ORCID, rights/eRights form), delivering every rebuttal promise within the 8-page budget, finalizing the video and de-anonymized archive, and passing production checks.MediaFără avertismente★ 1,4 K↓ —
- icde-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an IEEE ICDE research-track submission for round choice, Microsoft CMT setup, conflict declarations, the IEEE 12-page format, single-blind requirements, supplemental-material availability, the June/November two-round calendar, desk-reject triggers, and final-week sequencing for a data-engineering systems paper.DateFără avertismente★ 1,4 K↓ —
- knowledge-consolidationhuytieu/COG-second-brainBuild frameworks from scattered insights across all braindumps and notesProductivitateFără avertismente★ 1,3 K↓ —
- setupfcakyon/claude-codex-settingsThis skill should be used when the user asks "how to setup GitHub CLI", "configure gh", "gh auth not working", "GitHub CLI connection failed", "gh CLI error", or needs help with GitHub authentication.InginerieFără avertismente★ 1,2 K↓ —
- icalp-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ICALP (EATCS) campaign backward from its single annual February deadline, through abstract registration, the anonymous submission, the Track B rebuttal window, the April notification, and the LIPIcs camera-ready and presentation, and when coordinating a full-version (arXiv/ECCC) release alongside the anonymous submission.ProductivitateFără avertismente★ 1,4 K↓ —
- documenthashgraph-online/awesome-codex-pluginsRecord a decision, document existing code, or file a supplied research material. Modes: document decision (ADR, RFC, or rule), document code (spec, doc, guide, or scenario for existing behavior), document research (only when a finished report or one external material is already in hand). Use for 'we decided', 'record this decision', 'document why we chose X', 'make it our standard', 'draft an RFC', 'should we switch to Y' proposals, 'resolve the RFC', 'we accepted the proposal', 'document the auth module', 'capture how the payment system works', reference material, how-to instructions, or a user flow with examples over an existing spec. Name the type inside the subject to skip the type question. Planning a feature or an intended user journey → /archcore:plan. Checking docs against code or docs health → /archcore:review.ȘtiințăFără avertismente★ 1,5 K↓ —
- facct-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ACM FAccT project timeline from venue fit through abstract registration, OpenReview submission, the rebuttal window, the new Accept/Revise/Reject revise-and-resubmit round, two-round camera-ready, and in-person presentation, with backward-planning offsets for an interdisciplinary responsible-AI paper and honest handling of the single annual deadline.ProductivitateFără avertismente★ 1,4 K↓ —
ticket-authoring
rampstackco/claude-skills
De la autor
Write complete, ready-to-pull work items for an issue tracker: bugs, tasks, stories, spikes, and epics, each with the fields, attachments, and done test its type requires. Use this skill whenever the user wants to write a ticket, create a Jira issue, Linear issue, or GitHub issue, file a bug report, write a user story or acceptance criteria, scope a spike, open an epic, or break work into tasks. Triggers on write a ticket, create an issue, file a bug, bug report, user story, spike, epic, task breakdown, turn this into tickets, break this down, acceptance criteria, definition of ready, ready for dev, backlog item, capitalization stage. Also triggers when the user pastes a PRD, a spec, or a bug description and asks what to do with it, even if they never say the word ticket.
Instalare
npx skills add rampstackco/claude-skills --skill ticket-authoring -a claude-code
Se instalează în .claude/skills/ticket-authoring/ · 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 (10)
- README.md
- SKILL.md
- references/bug-template.md
- references/capitalization-guide.md
- references/definition-of-ready-checklist.md
- references/epic-template.md
- references/example-bug-and-story.md
- references/spike-template.md
- references/story-template.md
- references/task-template.md