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.415 skill-uri din 2.407 depozite · actualizat acum 2 ore
49.415 skill-uri
- vis-camera-readybrycewang-stanford/Awesome-Journal-SkillsUse when preparing an accepted IEEE VIS paper for its IEEE TVCG camera-ready, covering de-anonymization, the VGTC/TVCG template and journal metadata (DOI, ORCID, IEEE keywords/index terms), integrating the second-round required changes without scope creep, permanentizing open-materials links, the Open Practices disclosure form, and the Graphics Replicability Stamp handoff.ȘtiințăFără avertismente★ 1,4 K↓ —
- atc-supplementarybrycewang-stanford/Awesome-Journal-SkillsUse when deciding what belongs in the ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) two-page extended abstract, the 12-page paper body, the optional appendix, and the artifact — splitting content by review round and decision-criticality so nothing that decides acceptance lives where a reviewer is not required to read.ȘtiințăFără avertismente★ 1,4 K↓ —
- uai-camera-readybrycewang-stanford/Awesome-Journal-SkillsUse when converting an accepted UAI paper into its PMLR proceedings version, covering de-anonymization, final formatting against the UAI template, metadata for the PMLR volume, restoring public code and data links, poster and spotlight preparation for the conference, and sequencing work back from the camera-ready deadline.ȘtiințăFără avertismente★ 1,4 K↓ —
- orchestrating-agent-relayAgentWorkforce/relayThe canonical way to run agent-relay - self-bootstrap the local broker and autonomously spawn, monitor, and coordinate a team of worker agents without human intervention. Covers infrastructure startup, agent spawning, lifecycle monitoring, message-based reading via the relay MCP, and team coordination.DevOpsFără avertismente★ 1,1 K↓ —
- debug-live-issuehoangsonww/Claude-Code-Agent-MonitorDebug production-like issues in this repository with disciplined evidence gathering. Use when fixing failing workflows, regressions, flaky behavior, or data inconsistencies across hooks, API, DB, websocket, and UI.InginerieFără avertismente★ 1,1 K↓ —
- aeofcakyon/claude-codex-settingsThis skill should be used when the user asks to "build an AEO strategy", "improve AI search visibility", "track buyer prompts", "analyze AI citations", or "plan content for answer engines". Apply an evidence-led answer engine optimization (AEO/GEO) feedback loop to any product or service, prioritizing discovery by buyers who have not heard of it.PlanificareFără avertismente★ 1,2 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
- doca-upgradeNVIDIA/skillsChanging DOCA versions safely: upgrading or downgrading the host DOCA packages, refreshing the BlueField BFB, bumping the NGC DOCA container tag, or rolling back, with the discipline detect -> report -> ASK -> only then a guided upgrade. Trigger on "is there a newer DOCA", "I want the newest DOCA features, can I just apt upgrade in place", "should I move to the next release", "the upgrade stopped midway and dpkg is in a broken state", "my component is being deprecated, what now", or "roll me back", even without the word upgrade. Detect what is installed, find the newer release, report the gap, then STOP and ask for explicit confirmation; never upgrade automatically. Do not use it for a runtime error on an unchanged install (doca-debug). Version detection alone belongs to doca-version, first-time install to doca-setup, any hardware / firmware / reboot step to doca-hardware-safety, and public-docs or sunset routing to doca-public-knowledge-map.InginerieFără avertismente★ 3,9 K↓ —
- mcp-audithoangsonww/Claude-Code-Agent-MonitorAudit the configured MCP servers (user + project scope) via the Agent Monitor Config Explorer API: transport (stdio vs http), command/args and env variable names, headers, and the source file each definition came from. Reads /api/cc-config/mcp. Use when reviewing MCP integrations for hygiene, duplication, or unexpected transports.InginerieFără avertismente★ 1,1 K↓ —
- doca-comchNVIDIA/skillsUse this skill when the user is doing hands-on DOCA Comch work on a host + BlueField pair — bringing up host ↔ DPU PCIe control-plane messaging, picking server (DPU) vs client (host) roles, choosing slow-path send-task / recv-callback vs fast-path producer / consumer, querying max-msg-size or max-clients capabilities, registering connection callbacks, or debugging DOCA_ERROR_* returns from the Comch API. Trigger even when the user does not explicitly mention "DOCA Comch" or "Comm Channel" (renamed in DOCA 2.5) — typical implicit phrasings include "send a control message from host to BlueField over PCIe", "DPU can't see the host representor", "DOCA_ERROR_NOT_PERMITTED on server_create", "DOCA_ERROR_AGAIN on task_send submit", "connect callback never fires", or "stream bulk data from a host driver to a DPU agent". Refuse and route elsewhere for installing DOCA itself, BFB / firmware bring-up, non-Comch DOCA libraries, or deploying Comch apps at scale — those belong to other skills.DevOpsFără avertismente★ 3,9 K↓ —
- dac-supplementarybrycewang-stanford/Awesome-Journal-SkillsUse when deciding what belongs inside the six reviewed pages of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript versus in an external repository, given DAC's tight 6+1 budget, its references-only seventh page, the double-blind constraint on any linked material, and the absence of a formal reviewed-appendix or artifact-badging track.DesignFără avertismente★ 1,4 K↓ —
- hsb-appNVIDIA/skillsDiscover and run Holoscan Sensor Bridge example applications on a connected devkit. Filters available apps by the user's platform, HSB software version, board type, and sensors. Supports timed execution, failure analysis, code-edit suggestions, and iterative re-runs.RedactareFără avertismente★ 3,9 K↓ —
- huggingface-tool-builderhuggingface/skillsUse this skill when the user wants to build tool/scripts or achieve a task where using data from the Hugging Face API would help. This is especially useful when chaining or combining API calls or the task will be repeated/automated. This Skill creates a reusable script to fetch, enrich or process data.OficialInginerieFără avertismente★ 11,3 K↓ —
- os-ask-simplekharmanskyi/open-stepsALWAYS invoke this skill before asking the user any technical question or offering options, and whenever they ask to be asked in plain words - "ask simple", "ask me simply", "ask me in plain words" - in any language. ALWAYS invoke it too when the user asks for your view on a technical choice: whether it is worth doing, more than the problem needs, or replaceable by something simpler, and which option you would take. Invoke it even when the code makes the answer look obvious: the checks are what make the answer more than a guess. Rewrites the question in plain words and always ends with one marked recommendation. A structural choice first passes six checks, shown as a table: effort now, simpler substitute, extra work later, lock-in, over-engineering, easy to undo. Doing nothing is always weighed.InginerieFără avertismente★ 1,3 K↓ —
- os-whats-nextkharmanskyi/open-stepsALWAYS invoke this skill when the user asks what to do next, what is left, or what is blocked - "what's next", "what now", "what should we work on", "anything I can do" - in any language. This skill picks the next piece of work; when the user asks HOW to do a thing or says they do not understand what to do, that is os-step-by-step. Reads the last report, local changes, open pull requests and always the backlog. First finishes what is finished: verified-ready pull requests merge in the same pass. Then sorts the rest into doable-alone and needs-you, ending with one recommended next task in plain words - what it closes or unblocks. Never invents tasks.ProductivitateFără avertismente★ 1,3 K↓ —
- icml-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when stress-testing ICML experimental evidence before submission or rebuttal, including strong tuned baselines, mechanism-isolating ablations, seed variance and confidence intervals, compute disclosure, data leakage and split construction, reproducibility, negative results, and fit to ICML soundness, originality, and significance scoring.TestareFără avertismente★ 1,4 K↓ —
- podc-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when building the evidence for an ACM PODC paper — where "evidence" is a proof, not a benchmark. Covers matching upper and lower bounds, tightness arguments, model and assumption stress-tests, adversary-strength calibration, and the honest, clearly-optional role of any simulation in a distributed-computing-theory paper.TestareFără avertismente★ 1,4 K↓ —
- unity-agent-workflowshashgraph-online/awesome-codex-pluginsUse for AI-assisted Unity work that needs live repo discovery, project-derived routing, runtime-owner proof, runtime-visible output hard stops, runtime numeric proof for repeated visible-output failures, state-step guards, multi-agent scope ownership, modular C#/asmdef safety, UI/scene/visual asset gates, data-first content changes, validation, cleanup proof, or durable workflow rules. Best when agents must prove the actual folder/module/scene/prefab/runtime owner before editing, especially runtime UI, generated assets, code graphs, tutorial/state flows, guided selection/action flows, overlay/dim source-bound mistakes, coordinate conversions, focus/highlight/marker/HUD alignment, predictive lead aiming, ballistic trajectories, spatial IoU verification, or repeated "fix still not visible" failures.DesignFără avertismente★ 1,5 K↓ —
- iros-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing IROS experiments — real-robot trial counts, success criteria set in advance, reset procedures, failure taxonomies, baseline fairness on matched hardware, sim-to-real gap reporting, small-n statistics, and the claim-to-evidence ladder that embodied-systems reviewers apply before they trust a demo.AlteleFără avertismente★ 1,4 K↓ —
- icdt-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when deciding what counts as evidence for an ICDT (International Conference on Database Theory) result — matching-bound complexity analysis as the primary evidence, worked examples and counterexamples that establish separations, and, only for papers with an algorithmic contribution, a proportional and honestly-scoped experimental evaluation that does not pretend to be the contribution.DateFă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↓ —
- asc-xcode-buildrorkai/app-store-connect-cli-skillsBuild, archive, export, and manage Xcode version/build numbers with asc, including portable iOS compilation and packaging. Use when creating an IPA or PKG for App Store Connect, TestFlight, or registered-device release testing.TestareFără avertismente★ 1,1 K↓ —
- asc-crash-triagerorkai/app-store-connect-cli-skillsTriage TestFlight crashes, beta feedback, and performance diagnostics using asc. Use when the user asks about TF crashes, TestFlight crash reports, beta tester feedback, app hangs, disk writes, launch diagnostics, or wants a crash summary for a build or app.RedactareFără avertismente★ 1,1 K↓ —
- asc-release-flowrorkai/app-store-connect-cli-skillsOrchestrate App Store releases with asc, including staging a version, uploading or building an artifact, publishing, and submitting for review. Use when the user wants to prepare or execute a release. Keep Game Center item preparation in this skill; route other readiness failures, stuck submissions, cancellation, and retry decisions to asc-submission-health.InginerieFără avertismente★ 1,1 K↓ —
train-tickets
nano-muse/nanoMuse
BrowserActualizat acum 21 de ore
De la autor
nanoMuse: an open-source personal agent for every device you own. One agent with a name and a look of its own that does things, keeps working while the app is closed, remembers you, and asks before anything you cannot undo. On Android, iPhone and iPad, Windows / macOS / Linux and in the browser; your phone's screen and your computer as its hands.
Antetul nu a putut fi citit (invalid YAML: YAMLParseError: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Trains in China ); afișăm numele folderului.
Instalare
npx skills add nano-muse/nanoMuse --skill train-tickets -a claude-code
Se instalează în .claude/skills/train-tickets/ · Fiecare comandă descarcă skill-ul direct de pe GitHub cu utilitarul open source skills.
Fără descărcare: licența acestui skill (GPL-3.0) nu ne permite să-i redistribuim fișierele. Comenzile de instalare le iau direct de pe GitHub.
La ce are acces
Doar instrucțiuniNu am văzut acces la rețeaLicență: GPL-3.0
Verificări de siguranță pe SKILL.md
Niciun avertisment.
De ce 88
Securitate100
Proveniență82
Întreținere100
Licență80
Adopție56
Fișiere (1)
- SKILL.md