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.492 de skill-uri din 2.391 de depozite · actualizat acum 6 ore
49.492 de skill-uri
- trust-badges-generatorkostja94/marketing-skillsDeprecated compatibility entry for Trust Signals construction. This component is now maintained in Bricks; install and use component-builder to build a new Trust Signals.AlteleFără avertismente★ 1,1 K↓ —
- growth-funnelkostja94/marketing-skillsWhen the user wants to plan growth using the AARRR framework, diagnose growth bottlenecks, or map actions across the customer lifecycle. Also use when the user mentions "growth funnel," "AARRR," "pirate metrics," "acquisition activation retention," "customer lifecycle metrics," or "growth framework." For retention tactics, use retention-strategy.MarketingFără avertismente★ 1,1 K↓ —
- baoyu-translateJimLiu/baoyu-skillsThis skill should be used when the user asks to "translate", "翻译", "精翻", "translate article", "translate to Chinese", "translate to English", "改成中文", "改成英文", "convert to Chinese", "localize", "本地化", "refined translation", "精细翻译", "proofread translation", "快速翻译", "快翻", "这篇文章翻译一下", or provides a URL/file with translation intent. Supports three modes (quick/normal/refined) with custom glossary support.RedactareFără avertismente★ 27,3 K↓ —
- build-android-binarymicrosoft/power-platform-skillsCompile a PAM control's Android Kotlin module into the runtime-loadable DEX for a `.ppmplugin`. Creates a staged Gradle build with the pinned wrapper and `react-android` compile dependency, verifies manifest/module/package alignment and runtime-loading constraints, builds the release AAR, then runs `d8 --min-api 24`. Writes `ppmplugin/staging/android/<PascalName>Plugin.dex` and surfaces actionable Gradle or d8 failures. Requires JDK 17+ and Android SDK Build-Tools 35.0.0; `d8` is located from the SDK and system Gradle is optional. Run after /generate-ppmplugin-manifest and before /assemble-ppmplugin.RedactareFără avertismente★ 1,1 K↓ —
- competitor-researchkostja94/marketing-skillsWhen the user wants to analyze competitors for SEO, content, backlinks, or positioning. Also use when the user mentions "competitor analysis," "competitor research," "competitor keywords," "competitor backlinks," "link gap," "content gap," "competitor content," "competitive analysis," or "competitor comparison." For content roadmap, use content-strategy.ȘtiințăFără avertismente★ 1,1 K↓ —
- e2e-testinghashgraph-online/awesome-codex-pluginsPlaywright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.TestareFără avertismente★ 1,5 K↓ —Apare și în 1 alt depozit
- version-releasehoangsonww/Claude-Code-Agent-MonitorChoose and apply the correct semantic version bump for this repository. Use for every user-visible release, before merge when a change set should ship as patch, minor, or major, and whenever package/plugin/desktop version metadata must stay synchronized.AlteleFără avertismente★ 1,1 K↓ —
- research-competitorsgooseworks-ai/goose-skillsCompetitor research: what every main rival is running, launching, charging and saying now, what works for them, and what that means for you. Use when the marketer asks for competitor research or a teardown, "what ads are my competitors running", "how do they price", "find gaps and angles", "what changed this week" (a weekly watch), or "X just launched / shut down / cut prices" (react now). Also builds a sales battlecard, checks a competitor page's tools/pixels, or studies who engages with their LinkedIn posts. Delivers a readable report saved to the brand, so the next run reports what changed. Never copies their words or disparages them. Not for what people say about you or your market — use research-market; not for who your buyers are — use research-audience.ȘtiințăFără avertismente★ 1,3 K↓ —
- designhashgraph-online/awesome-codex-pluginsUse for standard or complex new work before coding or planning. Also handles vague goals — clarifies before designing.DesignFără avertismente★ 1,5 K↓ —
- openspec-update-changeMemeMeow-Studio/MemeMeowUpdate an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.RedactareFără avertismente★ 1,3 K↓ —
- openspec-update-changeMemeMeow-Studio/MemeMeowUpdate an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.RedactareFără avertismente★ 1,3 K↓ —
- openspec-apply-changeMemeMeow-Studio/MemeMeowImplement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.ProductivitateFără avertismente★ 1,3 K↓ —
- openspec-archive-changeMemeMeow-Studio/MemeMeowArchive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.ProductivitateFără avertismente★ 1,3 K↓ —
- openspec-exploreMemeMeow-Studio/MemeMeowEnter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.FinanțeFără avertismente★ 1,3 K↓ —Apare și în 1 alt depozit
- openspec-apply-changeMemeMeow-Studio/MemeMeowImplement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.ProductivitateFără avertismente★ 1,3 K↓ —Apare și în 1 alt depozit
- cikm-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the empirical program of a CIKM paper — matching evidence to the claim's lanes across retrieval, mining, and knowledge-management evaluation cultures, choosing datasets and baselines that survive a blended panel, isolating the boundary mechanism, and meeting applied-track deployment-evidence bars.DevOpsFără avertismente★ 1,4 K↓ —
- cav-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when revising a CAV (Computer Aided Verification) paper for a precise verification contribution on the first page, an explicit soundness/completeness statement, theorem-and-proof discipline in the LNCS page budget, fair benchmark claims, honest scope and limits, and double-blind wording for the anonymized categories.RedactareFără avertismente★ 1,4 K↓ —
- chi-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when drafting or revising the prose of an ACM CHI paper — contribution statements, structure for mixed reviewer audiences, participant voice, calibrated claims, accessible and bias-free writing, and length discipline in a venue that reviews words against contribution instead of pages.RedactareFără avertismente★ 1,4 K↓ —
- colm-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the empirical core of a COLM paper — contamination analysis for evaluation data, fair baselines under matched prompting and compute, pinned model versions and decoding parameters, uncertainty over runs and samples, scaling coverage, and honest reporting of API-model comparisons.ȘtiințăFără avertismente★ 1,4 K↓ —
- red-green-proofalirezarezvani/claude-skillsTurns a suspected bug into a proven one. Verify the cause against reality before claiming it, write a test that FAILS on the current code, apply the fix, watch it pass — then revert the fix and confirm the test goes red again, because a test that passes both ways proves nothing. Invoked bare after a debugging conversation, it takes the target from context rather than asking. Use when fixing a bug, investigating an incident, hardening a flaky area, or when asked to "add tests that reveal the bug". Triggers on "/red-green-proof", "prove the bug", "red-green", "make the test fail first", "is that test load-bearing", "reveal the bug with a test".TestareFără avertismente★ 29,3 K↓ —
- my-energy-mapmohitagw15856/pm-claude-skillsMap your real energy through the day and week, then match your tasks to it — hard things when you're sharp, easy things when you're not. Use when asked when should I do my hard work, map my energy, why am I so unproductive at certain times, or schedule around my focus. Produces a picture of your energy peaks, troughs, and patterns from your own observations, a task-to-energy matching plan (deep work at peaks, admin at troughs), the traps you're currently falling into, and a realistic daily shape — because fighting your natural rhythm wastes your best hours on your worst tasks.PlanificareFără avertismente★ 1,5 K↓ —
- acl-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when revising an ACL paper for computational-linguistics house style, covering task-first framing, linguistic examples tied to quantitative error analysis, scoping language claims to tested languages, LLM-era claim discipline, anonymous self-reference, Limitations prose, and compressing into the 8-page or 4-page ACL format.RedactareFără avertismente★ 1,4 K↓ —
- acl-supplementarybrycewang-stanford/Awesome-Journal-SkillsUse when organizing appendices and supplementary material for an ACL paper under ACL Rolling Review, covering the mandatory Limitations and optional ethics sections, appendices after references, anonymized software and data archives, the no-cloud-links rule, and deciding what must stay in the 8-page or 4-page body.ȘtiințăFără avertismente★ 1,4 K↓ —
- acmmm-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning the end-to-end ACM MM (ACM Multimedia) campaign calendar — from thematic-area scoping and track choice, through the April OpenReview abstract/paper/supplement chain, the June anonymous rebuttal, the July decision, the August camera-ready, and the November presentation in Rio, with the right skill invoked at each stage.ProductivitateFără avertismente★ 1,4 K↓ —
seo-offpage
rampstackco/claude-skills
MarketingActualizat 27 oct. 2026
De la autor
Plan and execute off-page SEO including link building, digital PR, brand mentions, citation building, and external authority signals. Use this skill whenever the user wants to build backlinks, plan a digital PR campaign, list local citations, run guest post outreach, develop linkable assets, recover lost links, or audit a backlink profile for risk. Triggers on link building, backlinks, digital PR, brand mentions, citation building, guest post, outreach, linkable asset, broken link building, HARO, podcast outreach, off-page SEO, anchor text, link velocity, toxic backlinks, disavow. Also triggers when the user is trying to grow domain authority or earn coverage.
Instalare
npx skills add rampstackco/claude-skills --skill seo-offpage -a claude-code
Se instalează în .claude/skills/seo-offpage/ · 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 88
Securitate100
Proveniență76
Întreținere100
Licență100
Adopție49
Fișiere (4)
- README.md
- SKILL.md
- references/linkable-assets-guide.md
- references/outreach-templates.md