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.399 de skill-uri din 2.375 de depozite · actualizat acum 15 minute
49.399 de skill-uri
- dsh-docNouqufei1993/skills-hub创建或维护工程文档、设计决策、事故复盘、归档提案或产品迁移指南时使用，保留事实依据、实际备选方案和准确状态。AlteleFără avertismente★ 1,9 K↓ —
- blucliLeoYeAI/agent-master-skillsBluOS CLI (blu) for discovery, playback, grouping, and volume.InginerieFără avertismente★ 2,2 K↓ —
- linux-shell-scriptingzebbern/claude-code-guideThis skill should be used when the user asks to "create bash scripts", "automate Linux tasks", "monitor system resources", "backup files", "manage users", or "write production shell scripts". It provides ready-to-use shell script templates for system administration.RedactareFără avertismente★ 4,7 K↓ —
- shodan-reconnaissancezebbern/claude-code-guideThis skill should be used when the user asks to "search for exposed devices on the internet," "perform Shodan reconnaissance," "find vulnerable services using Shodan," "scan IP ranges with Shodan," or "discover IoT devices and open ports." It provides comprehensive guidance for using Shodan's search engine, CLI, and API for penetration testing reconnaissance.SecuritateFără avertismente★ 4,7 K↓ —
- imagensickn33/agentic-awesome-skillsAI image generation skill powered by Google Gemini, enabling seamless visual content creation for UI placeholders, documentation, and design assets.DesignFără avertismente★ 49,1 K↓ —
- dev-requirementscodeaholicguy/ai-devkitAI DevKit · Requirements phase guidance for starting features and reviewing requirements. Use when the user wants to capture a new requirement, clarify product scope, initialize feature docs, review requirements, or run dev-lifecycle phases 1-2.PlanificareFără avertismente★ 1,7 K↓ —
- scenario-workflowsscenario-labs/skillsUse when a task involves running a Scenario workflow through MCP, including anything the user calls a Scenario app, a saved pipeline, or a multi-step generation graph. Triggers include listing workflows, building workflow_run's inputs object, pricing a run with a dry run, approving or rejecting a stuck approval node, a run rejected for input length, or a workflows_list reply flooding the context. Creating or editing graphs is scenario-workflow-authoring. Keywords: workflow, app, approval gate.RedactareFără avertismente★ 1,9 K↓ —
- technical-writercodeaholicguy/ai-devkitAI DevKit · Review and improve documentation for novice users. Use when users ask to review docs, improve documentation, audit README files, evaluate API docs, review guides, or improve technical writing.RedactareFără avertismente★ 1,7 K↓ —
- agent-managementcodeaholicguy/ai-devkitAI DevKit · Manage running AI agents with ai-devkit agent commands. Use when an agent needs to identify itself, list agents, start workers, inspect agent detail, assign work, group agents, resume sessions, stop agents, or delegate work to other agents.AlteleFără avertismente★ 1,7 K↓ —
- slideopssickn33/agentic-awesome-skillsTurn a repository into a cited HTML slide deck and detect the day it drifts from the code. Citations record file, lines, and hash; a stdlib check reports CURRENT, MOVED, or CHANGED.DocumenteFără avertismente★ 49,1 K↓ —
- write-a-postmorteminkeep/open-knowledgeWrite a blameless incident postmortem under postmortems/ following the Google SRE shape — evidence-based timeline, trigger vs root cause vs symptom, contributing factors, what went well, and owned+dated+verifiable action items. Read when asked to write a postmortem, do an incident review, run a root cause analysis, write up the outage, retro on the outage, or when the user says we had an incident and wants it documented. Do NOT read to frame a proposal (use frame-a-proposal), write a spec (use write-a-spec), record a decision (use record-a-decision), or review a design (use review-a-design) — a postmortem documents an incident that already happened, it does not propose, specify, decide, or critique future work.RedactareFără avertismente★ 4,8 K↓ —
- remote-from-telegramcodeaholicguy/ai-devkitAI DevKit · Connect the current agent session to an available Telegram channel bridge.AlteleFără avertismente★ 1,7 K↓ —
- dev-prcodeaholicguy/ai-devkitAI DevKit · Publish a ready feature branch for review. Use when the user wants to sync, push, and open or update a code review request on GitHub, GitLab, or another Git host.InginerieFără avertismente★ 1,7 K↓ —
- dev-guide-generatorzebbern/claude-code-guideGenerates complete technical tutorials from prerequisites and environment setup to core steps, troubleshooting, and a final cheatsheet. Trigger on requests to write a tutorial, create a setup guide, organize steps for beginners, or keywords like step-by-step, quickstart, or how-to guide.RedactareFără avertismente★ 4,7 K↓ —
- kaltstart-triageKlotzkette/claude-fuer-deutsches-rechtFür Kaltstart Triage: routet Rolle, Frist, Unterlagen und Fachschritt; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: Arbeitsrecht.AlteleFără avertismente★ 1,8 K↓ —
- blog-writeAgriciDaniel/claude-blogWrite a new blog article from scratch for Google rankings and AI citations, then take it through the delivery gates. Generates the full article with template selection, answer-first formatting, Key Takeaways box, sourced statistics, licensed images, built-in SVG charts, optional FAQ and internal linking, in MDX, markdown or HTML. Use when the user asks to write a new blog post or article from a topic or brief ("write a blog post", "draft a new article", "/blog write"). Not for editing an existing post (blog-rewrite), and not for a standalone outline, brief or research request.RedactareFără avertismente★ 2,6 K↓ —
- leasing-agbKlotzkette/claude-fuer-deutsches-rechtFür Leasing AGB: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt.AlteleFără avertismente★ 1,8 K↓ —
- mex-inboxmex-memory/mexDraft and review contributions to existing MEX project knowledge. Use when the user asks to capture a discussion or decision in project knowledge, propose an addition or correction for team review, or explicitly invokes /mex-inbox or $mex-inbox. Also supports existing Spec proposals. Do not activate for brainstorming alone, routine GROW upkeep, email inboxes, session logs, or handoffs.PlanificareFără avertismente★ 1,8 K↓ —Apare și în 1 alt depozit
- monetizing-innovationwondelai/skillsDesign products and pricing around validated willingness to pay, from Ramanujam & Tacke's "Monetizing Innovation". Use when the user mentions "pricing", "how much should we charge", "willingness to pay", "pricing page", "packaging", "freemium vs free trial", "are we leaving money on the table", "nobody buys at this price", "price increase", or "good-better-best". Also trigger when designing or auditing pricing and packaging, validating willingness to pay before building, segmenting customers by value, or choosing between subscription, usage-based, and freemium models. Covers price-before-product, willingness-to-pay talks, the four failures (feature shock, minivation, hidden gem, undead), leader/filler/killer packaging, and behavioral pricing. For offers and guarantees, see hundred-million-offers. For what customers value, see jobs-to-be-done.DesignFără avertismente★ 2,6 K↓ —Apare și în 2 alte depozite
- record-a-decisioninkeep/open-knowledgeRecords an architecture decision as a Nygard/MADR-shaped ADR under decisions/ — capturing the context that forced the choice, the options weighed, the decision itself, and its consequences in both directions, plus the supersedes chain that keeps a decision log honest. Read when asked to record an architecture decision, write an ADR, log the decision we made, document why we chose X over Y, capture this decision for the record, or supersede an old decision with a new one. Do NOT read to frame a proposal or explore an idea not yet decided (frame-a-proposal), to write a spec or implementation plan (write-a-spec), to write an incident postmortem (write-a-postmortem), or to judge whether a design is sound (review-a-design). This skill records a decision already made; it does not make one.DesignFără avertismente★ 4,8 K↓ —
- review-a-designinkeep/open-knowledgeReviews whether a design is SOUND — solving the right problem, derived from its stated goals and constraints — and emits ranked, evidence-backed findings, not edits. Read when asked to 'review this design', 'is this design sound', 'pressure-test this proposal', 'do a design review', 'does this solve the right problem', 'poke holes in this spec', 'should we build this', or to critique a proposal / spec / ADR / architecture or product decision. Do NOT read when the user wants to AUTHOR one of these — routing a new proposal is frame-a-proposal, a spec is write-a-spec, a decision record is record-a-decision, a postmortem is write-a-postmortem. Do NOT read for code review of a diff, or to fact-check individual claims (that is a correctness pass, a different job).DesignFără avertismente★ 4,8 K↓ —
- energievertraegeKlotzkette/claude-fuer-deutsches-rechtFür Energie-Verträge — Strukturierung und Prüfung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt.AlteleFără avertismente★ 1,8 K↓ —
- remove-technical-debtwondelai/skillsGuided journey from a large aged codebase everyone fears to touch to one that is safe to change, legible, bounded, and resilient - paid down in place without a rewrite. Orchestrates eight skills phase by phase - working-with-legacy-code, refactoring-patterns, clean-code, software-design-philosophy, clean-architecture, pragmatic-programmer, release-it, domain-driven-design - asking the user questions at every decision point and recording results in the project docs/ folder (TESTING.md, TECH-DEBT.md, REMOVE-TECHNICAL-DEBT-PLAN.md) so the journey resumes across sessions. Use when the user wants to tame a legacy codebase, pay down technical debt safely, avoid a big-bang rewrite, or says 'we are afraid to touch this code'. For a fresh vibe-coded prototype, improve-code-quality; for greenfield structure, design-code-architecture; for a product-and-UX pass, improve-app; to optimize a working codebase for speed, architecture-optimization. For one framework in isolation, invoke that skill directly.TestareFără avertismente★ 2,6 K↓ —Apare și în 2 alte depozite
- ai-devkit-setupcodeaholicguy/ai-devkitAI DevKit · Check local AI DevKit readiness and run setup only when status shows onboarding or harness integration gaps.AlteleFără avertismente★ 1,7 K↓ —
inkos
LeoYeAI/agent-master-skills
DateActualizat acum 18 ore
De la autor
Autonomous novel writing CLI agent - use for creative fiction writing, novel generation, style imitation, chapter continuation/import, EPUB export, AIGC detection, and fan fiction. Native English support with 10 built-in English genre profiles (LitRPG, Progression Fantasy, Isekai, Cultivation, System Apocalypse, Dungeon Core, Romantasy, Sci-Fi, Tower Climber, Cozy Fantasy). Also supports Chinese web novel genres (xuanhuan, xianxia, urban, horror, other). Multi-agent pipeline, two-phase writer (creative + settlement), 33-dimension auditing, token usage analytics, creative brief input, structured logging (JSON Lines), multi-model routing, and custom OpenAI-compatible provider support.
Instalare
npx skills add LeoYeAI/agent-master-skills --skill inkos -a claude-code
Se instalează în .claude/skills/inkos/ · 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 89
Securitate100
Proveniență80
Întreținere100
Licență100
Adopție53
Fișiere (2)
- SKILL.md
- _meta.json