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 6 minute
48.351 de skill-uri
- writehashgraph-online/awesome-codex-pluginsUse for marketing, social, replies, product copy, launch copy, and writing in the user's voice when their Emulo writing profile should guide the task. Do not use for unrelated execution or UI/UX design alone.RedactareFără avertismente★ 1,5 K↓ —Apare și în 2 alte depozite
- autoreviewopenclaw/crabboxStructured code review through the shared OpenClaw agent-skills installation.InginerieFără avertismente★ 1,5 K↓ —
- minutes-x1-send-meetingsilverstein/minutesSend one of the user's own Minutes meetings to their X1 household for review. Use when the user wants a meeting's summary, decisions, action items, and open questions to reach X1 so they can confirm what belongs in their household record. X1 asks the user to approve the send, and nothing reaches the household record until they confirm each item. Never use it for a restricted meeting, a transcript, or someone else's meeting.InginerieFără avertismente★ 1,6 K↓ —Apare și în 1 alt depozit
- minutes-x1-closeoutsilverstein/minutesPrepare a sourced Minutes meeting outcome for human-governed closeout of existing X1 work. Use when the user wants a meeting decision or commitment to close, defer, escalate, or retire a specific X1 coordination thread. Never use it to infer settlement, move money, contact anyone, or close X1 work automatically.PlanificareFără avertismente★ 1,6 K↓ —Apare și în 1 alt depozit
- minutes-mcp-recallsilverstein/minutesRoute meeting-recall questions to the right Minutes MCP tool.AlteleFără avertismente★ 1,6 K↓ —Apare și în 1 alt depozit
- minutes-lintsilverstein/minutesHealth-check your meeting knowledge for contradictions, stale commitments, and decision conflicts. Use when the user asks "any conflicts in my meetings", "check for stale action items", "lint my meetings", "consistency check", "are there contradictions", or wants to audit their decision history.AlteleFără avertismente★ 1,6 K↓ —Apare și în 1 alt depozit
- minutes-graphsilverstein/minutesPolicy-safe relationship rankings, commitments, aliases, person profiles, and topic research. Always use Minutes' bounded native CLI surfaces; never build or read a durable graph cache.ȘtiințăFără avertismente★ 1,6 K↓ —Apare și în 1 alt depozit
- ops-inspectorTencentCloudBase/CloudBase-AI-ToolkitAIOps-style CloudBase inspection skill. Use when users need health checks, log diagnosis, alarm interpretation (CPU alert normal?, peak QPS), metrics via queryEnv(action=metrics), fault playbooks for 429 / AI model 429 / function timeout / function 404 / ACCESS_TOKEN_INVALID / zero invocations, or a scheduled patrol that reports only new or worse findings. Triggers on 巡检, 诊断, 告警, 峰值 QPS, 限频, 调用量为 0, 定时巡检, 每天检查, 值守, troubleshooting.AlteleFără avertismente★ 1,2 K↓ —Apare și în 4 alte depozite
- brooks-harnesshyhmrright/brooks-lintMaintenance orchestrator for the brooks-lint plugin itself. Runs a sequential subagent pipeline — author → eval → QA → trigger-audit → release — to add or edit a skill, refresh the eval suite, keep the four manifests + all README translations + CHANGELOG + AGENTS/GEMINI in sync, audit trigger boundaries, and cut releases. Drives the five agents in .codex/agents/ (skill-author, eval-curator, consistency-qa, trigger-boundary-auditor, release-manager). Triggers when the maintainer asks to work ON brooks-lint itself: "add a new skill", "edit the brooks-debt guide", "update the eval suite", "fix the trigger descriptions", "make this change and validate it", "release brooks-lint", "bump and publish", and follow-ups: "re-run", "re-validate", "update that skill", "redo the audit", "do the X part again". Do NOT trigger for: USING the brooks-lint analysis skills on some target codebase (that's brooks-review / brooks-audit / brooks-debt / brooks-test / brooks-health / brooks-sweep); generic questions about brooks-lint tTestareFără avertismente★ 1,6 K↓ —
- new-skillhyhmrright/brooks-lintScaffold a new brooks-lint analysis skill so it passes `npm run validate` and `npm run evals` on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends paired eval scenarios. Triggers when the maintainer asks to "add a new skill", "scaffold a skill", or "create a brooks-lint mode". Do NOT trigger for: editing an existing skill's content, adding a single eval to an existing skill, or authoring skills for some other plugin.RedactareFără avertismente★ 1,6 K↓ —
- brooks-reviewhyhmrright/brooks-lintPR code review that surfaces decay risks, design smells, and maintainability issues with concrete Symptom → Source → Consequence → Remedy findings, drawing on twelve classic engineering books. Triggers when: user asks to review code, check a PR, shares a diff or pastes code asking "does this look right?" / "any issues here?" / "ready to merge?", or asks for feedback on a function, class, or file. Also triggers when user mentions: code smells / refactoring / clean architecture / DDD / SOLID principles / Hyrum's Law / deep modules / tactical programming / conceptual integrity / Brooks's Law / Mythical Man-Month / second system effect. Do NOT trigger for: questions about how to write code from scratch, language syntax questions, or framework/tool questions where no existing code is shared.InginerieFără avertismente★ 1,6 K↓ —
- brooks-audithyhmrright/brooks-lintArchitecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books. Triggers when: user asks to audit architecture, review folder/module structure, check for circular imports, understand how the codebase is organized, or asks "does this follow clean architecture?" or "why does everything depend on everything?". Also triggers for onboarding requests: "explain this codebase to a new developer" or "give me a codebase tour" (use onboarding mode). Do NOT trigger for: PR-level code review (use brooks-review) or line-level refactoring questions — this skill analyzes structural/module-level concerns, not individual functions.PlanificareFără avertismente★ 1,6 K↓ —
- brooks-testhyhmrright/brooks-lintTest quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow execution, poor readability. Triggers when: user asks about test quality, shares test files for review, or expresses frustration: "tests keep breaking whenever I change anything", "our tests take forever", "tests pass but bugs still reach production", or "we have too many mocks". Do NOT trigger for: writing new tests from scratch (use the regular test-writing workflow) or testing framework/syntax questions — this skill reviews an existing suite for structural quality problems, not individual test authoring.TestareFără avertismente★ 1,6 K↓ —
- weekly-rollupmohitagw15856/pm-claude-skillsRoll a week of daily reports and agent activity into one honest weekly summary: trajectory against goals, what shipped with proof, the recurring blocker, and what to change next week. Use when asked for a weekly rollup, summarise my week, what did the agent accomplish this week, or a Friday wrap-up from my daily reports. Produces a 12-line weekly rollup in the shared status vocabulary: shipped versus planned, the pattern in the blockers, and one concrete change for next week.PlanificareFără avertismente★ 1,5 K↓ —
- second-brain-lintundefined-ui/second-brain-osAudit a second-brain vault for structural problems and repair them: broken wikilinks, orphan pages, empty stubs, frontmatter that violates the schema, near-duplicate pages, and stale index entries. Use this skill whenever the user asks to lint, clean, audit or check the health of their vault, says pages feel messy or links are broken, after a large bulk import, or when a scheduled maintenance run fires. Do NOT use for ingesting new sources, for answering questions from the vault, or for rewriting page content that is structurally fine but reads badly.AlteleFără avertismente★ 1,2 K↓ —
- second-brain-quizundefined-ui/second-brain-osGenerate questions from the user's own concept pages so they can find out what they saved but never learned, and compare their answers against what the pages say. Use this skill when the user wants to test themselves, revise, make flashcards from their notes, or asks what they have forgotten. Do NOT use for generic quizzing on a topic the vault does not cover, or for answering a question from the vault.TestareFără avertismente★ 1,2 K↓ —
- second-brain-graphundefined-ui/second-brain-osAnalyse the vault's link graph and report on its shape: orphan rate, average degree, components, hubs, bridges and clusters, with what each number means for retrieval. Use this skill when the user asks about the health or structure of their graph, wants metrics, asks which pages are most connected or most isolated, or asks whether the vault is fragmented. Do NOT use for fixing what it finds, which is second-brain-lint, or for answering a content question.AlteleFără avertismente★ 1,2 K↓ —
- second-brain-mergeundefined-ui/second-brain-osMerge two pages that describe the same thing, preserving every distinct claim, redirecting inbound links, and recording the merge. Use this skill when the user approves a duplicate merge, says "these are the same page", "merge X into Y", or asks to clean up near-duplicates that a lint run proposed. Do NOT use to merge pages on your own judgement, to delete a page outright, or to split one page into several.AlteleFără avertismente★ 1,2 K↓ —
- second-brain-queryundefined-ui/second-brain-osAnswer a question from a second-brain vault by reading its own pages, citing the pages used, and saying plainly when the vault does not contain the answer. Use this skill whenever the user asks what they know about a topic, what they have read on something, what connects two ideas, what they have changed their mind about, or asks any question that should be answered from their own notes rather than general knowledge. Do NOT use for ingesting new material, for general questions the vault has nothing to do with, or when the user explicitly wants an answer from the open web.ProductivitateFără avertismente★ 1,2 K↓ —
- design-buildhashgraph-online/awesome-codex-pluginsExecute a design plan produced by /design -- implements each node against its embedded measurement spec and gates every task on the project's build or tests under a bounded retry budget. Runs with Figma disconnected; the plan carries every number it needs. --auto runs the whole loop without a prompt.DesignFără avertismente★ 1,5 K↓ —
- redis-coreredis/agent-skillsCore Redis modeling guidance — choose the right data structure (String, Hash, List, Set, Sorted Set, JSON, Stream, Vector Set) and use consistent colon-separated key names. Use when designing a Redis data model, caching objects, deciding between Hash and JSON, building counters, leaderboards, membership sets, or session stores, or when reviewing/cleaning up Redis key naming.OficialAlteleFără avertismente★ 172↓ —Apare și în 1 alt depozit
- aeoNoufcakyon/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↓ —
- verify-optimistic-updatereticlehq/reticleProve a UI that updates before the server answers puts things back and says so when the request fails, and keeps the change when it succeeds. Use when a like, toggle, rename, reorder, delete or add-to-cart updates instantly, when an optimistic update was added or changed, or when a user reports a change that "saved" but was gone after a reload.DesignFără avertismente★ 1,3 K↓ —
- verify-unattendedreticlehq/reticleInstall, instrument and verify a web app end to end without pausing for a human. Use in an autonomous or goal-mode agent, in CI, or in any client that asks for approval on every command: it never says "restart your client" or "open a browser", because it takes a route that needs neither. Prefer the normal reticle skill when a human is present and can answer.BrowserFără avertismente★ 1,3 K↓ —
seo-monitoring
kostja94/marketing-skills
MarketingActualizat 26 oct. 2026
De la autor
Compatibility pointer for recurring SEO monitoring; maintained in Open Analytics.
Instalare
npx skills add kostja94/marketing-skills --skill seo-monitoring -a claude-code
Se instalează în .claude/skills/seo-monitoring/ · 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țiuniFolosește rețeauaLicență: MIT
Verificări de siguranță pe SKILL.md
Niciun avertisment.
De ce 88
Securitate100
Proveniență76
Întreținere100
Licență100
Adopție49
Fișiere (1)
- SKILL.md