AGENT SKILLS · EQUIPO DE MISIÓN
Agent Skills útiles ordenados por uso real
Compara Skills verificados por función, contenido del paquete, instalaciones y fiabilidad de la fuente antes de añadirlos.
- ALCANCE DEL CATÁLOGO
- VERIFICADO
- Skills
- 22.847
- repositorios
- 3523
- última sincronización
- 3 nov 2026
samberdeveloper-journey-map
Maps the developer journey for one audience segment - discovery, trial, adoption, contribution, advocacy - as a stage-by-stage table where each stage carries an exit event, a named owner, cited friction evidence and one signal, and names the single leak worth fixing next. Use whenever someone asks what their developer journey looks like, wants a developer adoption funnel or journey map, asks why developers try the product but never reach production, where adoption drops off, who owns each step o
- Instalaciones / 1h
- 17
- GitHub Stars
- 6
- Actualizado
- 26 oct
samberdeveloper-keyword-research
Builds a prioritized keyword list for technical search queries (error strings, "how to X in Y" tasks, integration intents, comparisons, migrations) mined from docs search logs, support tickets, issue trackers and first-party query data rather than keyword-tool volume. Use whenever the user asks what developers actually search for, wants keywords for a developer tool, API, SDK or docs site, an error-message keyword list, demand sizing for a technical topic, or which docs pages to create from sear
- Instalaciones / 1h
- 17
- GitHub Stars
- 6
- Actualizado
- 26 oct
samberdeveloper-segmentation
Cuts a developer audience into a few named, sized and ranked segments - the two dimensions worth cutting on, a size range with a confidence tier, the user/champion/approver/buyer split inside each, a weighted score, one primary and one secondary segment, and a written anti-segment. Use whenever someone asks who their developers actually are, which developer audience to serve first, how big a language ecosystem or persona is, whether to target hobbyists or enterprise platform teams, who signs whe
- Instalaciones / 1h
- 17
- GitHub Stars
- 6
- Actualizado
- 26 oct
samberdevtools-business-model
Chooses the business model for a developer tool - proprietary SaaS, open core, hosted open source, support and LTS subscription, dual licensing, source-available, consumption metering, marketplace take-rate, OEM licensing - and the go-to-market each one forces. Use whenever a founder or exec asks how a developer tool should make money, whether open core or a managed cloud fits better, where the line between free and paid belongs, whether to open-source the product at all, or why adoption is high
- Instalaciones / 1h
- 17
- GitHub Stars
- 6
- Actualizado
- 26 oct
sambeross-contributor-onboarding
Designs and verifies the path a stranger walks to their first merged contribution on an open-source project - the CONTRIBUTING file, the good-first-issue queue, a clone-to-passing-tests command that works cold, and the first-pull-request review and recognition loop, scored against a blocking-plus-weighted rubric. Use whenever someone says "nobody contributes to my project", "write a CONTRIBUTING.md", "our good first issues get no takers", "first-time contributors disappear", "contributor onboard
- Instalaciones / 1h
- 17
- GitHub Stars
- 6
- Actualizado
- 26 oct
sambeross-governance
Chooses and documents an open-source project's governance model - decision rights, maintainer roles and promotion, voting and consensus rules, conflict escalation, succession, trademark and asset control, and whether to join a foundation or fiscal host. Use whenever someone asks who decides in their project, wants to write or fix a GOVERNANCE.md, is adding or removing maintainers, worries about bus factor or a single-vendor-controlled project, faces a deadlocked or contested decision, or is prep
- Instalaciones / 1h
- 17
- GitHub Stars
- 6
- Actualizado
- 26 oct
sambeross-issue-triage
Designs an issue and pull-request triage system a maintainer team can sustain - response targets sized against real capacity, the label taxonomy, intake cuts through structured forms and off-tracker routing, a separate security-report path, triage duty assignment, and the closing, staleness and volume-gating policy. Use whenever someone says "our issue tracker is out of control", "design an issue triage process", "set up labels for our repo", "we have 900 open issues", "should we run a stale bot
- Instalaciones / 1h
- 17
- GitHub Stars
- 6
- Actualizado
- 26 oct
sambeross-license-strategy
Chooses an open-source project's license and contribution policy as one decision - permissive vs weak, strong or network copyleft, dependency-driven compatibility constraints, DCO vs CLA vs nothing, dual licensing and open core, source-available options (BUSL, FSL, Elastic License, SSPL), and the fork risk of relicensing. Use whenever someone asks which license to pick, whether MIT, Apache-2.0, GPL or AGPL fits, whether to require a CLA or a DCO sign-off, how to relicense an existing project, wh
- Instalaciones / 1h
- 17
- GitHub Stars
- 6
- Actualizado
- 26 oct
sambertech-employer-branding
Designs an employer-brand strategy for attracting software engineers - the engineering EVP, the channel plan (engineering blog, OSS presence, referrals, conference talks, compensation-transparency artifacts), a verification-surface audit (employer-review sites, compensation databases, anonymous forums), and the measurement baseline. Use whenever someone raises "engineering employer brand", "why can't we attract engineers", "developer hiring content strategy", "should we publish salary bands", "t
- Instalaciones / 1h
- 17
- GitHub Stars
- 6
- Actualizado
- 26 oct
samberversion-migration-guide
Writes or audits the migration guide for a breaking change - what breaks, ordered by blast radius, with a detection signal and before/after code per entry, a deprecation timeline, the codemod's coverage boundary, and verification by a cold upgrade of a real project. Use whenever someone mentions a migration guide, an upgrade guide, a breaking-changes page, a major version bump, "how do we tell users about v3", an API version cutover, a deprecation or sunset notice, or a codemod or compat build -
- Instalaciones / 1h
- 17
- GitHub Stars
- 6
- Actualizado
- 26 oct
rmyndharisagent-orchestration-improve-agent
Systematic improvement of existing agents through performance analysis, prompt engineering, and continuous iteration.
- Instalaciones / 1h
- 17
- GitHub Stars
- 1,9 mil
- Actualizado
- 14 oct
troykellyautonomous-orchestration
Use when user requests autonomous operation across multiple issues. Orchestrates parallel workers using Task tool, monitors with TaskOutput, handles SLEEP/WAKE cycles, and works until scope is complete without user intervention.
- Instalaciones / 1h
- 17
- GitHub Stars
- 12
- Actualizado
- 13 ene
deckardgertanstack-start-best-practices
TanStack Start best practices for full-stack React applications. Server functions, middleware, SSR, authentication, and deployment patterns. Activate when building full-stack apps with TanStack Start.
- Instalaciones / 1h
- 17
- GitHub Stars
- 224
- Actualizado
- 9 sept
gbasinclanker-discipline
Catches state bloat, grab-bag models, and mutation ambiguity from AI coding agents. Use when reviewing state types, boolean flags, optional-field models, or mutable data patterns.
- Instalaciones / 1h
- 17
- GitHub Stars
- 22
- Actualizado
- 23 mar
5dive-ai5dive-cli
Operate the local 5dive runtime: coordinate sibling agents and inspect or update shared tasks. Use for delegation, inter-agent messaging and task-queue operations; use 5dive-cli-extras for runtime administration beyond those.
- Instalaciones / 1h
- 16
- GitHub Stars
- 1
- Actualizado
- 3 nov
5dive-aicompile-knowledge
Compile durable, judgement-shaped knowledge into interlinked markdown — atomic files, [[wiki-links]], a maintained index. Use when persistence is asked for explicitly ("save this", "write it to the wiki") or when the work produced a decision record, a cause, or a gap analysis; ordinary factual answers and routine task results are not a trigger.
- Instalaciones / 1h
- 16
- GitHub Stars
- 1
- Actualizado
- 3 nov
cloudai-xthreejs-react-three-fiber
Building three.js scenes from React with React Three Fiber and drei: renderer setup, the scene graph as JSX, frame-loop, state and loading hooks, pointer events, and adaptive performance, on WebGL or with WebGPU and TSL. Use when writing React components that render three.js.
- Instalaciones / 1h
- 16
- GitHub Stars
- 3,8 mil
- Actualizado
- 19 oct
samberdeveloper-live-demo-design
Engineers a technical demo so it survives the stage - risk triage, the fidelity tier it should run at, independently enterable checkpoints, a one-command environment reset, offline mode, a recorded fallback and rehearsed recovery lines, shipped as a demo runbook with a pre-flight checklist. Use whenever the user mentions a live demo, live coding, demo reliability or a fallback plan, "my demo broke on stage", whether to demo live or pre-record, a demo environment reset, a clean demo laptop, a dem
- Instalaciones / 1h
- 16
- GitHub Stars
- 6
- Actualizado
- 26 oct
lobehubzustand
Use for Zustand stores: state shapes and type sources, state-only stores with xActions classes, replica-backed list/detail data (@lobechat/replica), selectors, optimistic writes, and legacy slice/internal action composition.
- Instalaciones / 1h
- 16
- GitHub Stars
- 83,4 mil
- Actualizado
- 20 oct
secondskytailwind-v4-shadcn
| Production-tested setup for Tailwind CSS v4 with shadcn/ui, Vite, and React. Use when: initializing React projects with Tailwind v4, setting up shadcn/ui, implementing dark mode, debugging CSS variable issues, fixing theme switching, migrating from Tailwind v3, or encountering color/theming problems. Covers: @theme inline pattern, CSS variable architecture, dark mode with ThemeProvider, component composition, vite.config setup, common v4 gotchas, and production-tested patterns.
- Instalaciones / 1h
- 16
- GitHub Stars
- 231
- Actualizado
- 20 oct
deckardgertanstack-router-best-practices
TanStack Router best practices for type-safe routing, data loading, search params, and navigation. Activate when building React applications with complex routing needs.
- Instalaciones / 1h
- 16
- GitHub Stars
- 224
- Actualizado
- 9 sept
samberapi-integration-surface-strategy
Decide which integration surfaces a platform offers external developers and AI agents - REST, GraphQL, gRPC, SQL access, bulk data sharing, webhooks, SDKs, CLI, MCP, embedded components - and in what build order, sequenced by reversal cost and audience rather than novelty. Use whenever the user mentions which API to build first, adding a GraphQL or MCP layer, an integration-surface roadmap, API-first vs embedded-first, or a missing surface blocking deals - even if they never say "integration sur
- Instalaciones / 1h
- 16
- GitHub Stars
- 3
- Actualizado
- 14 oct
samberintegration-partnership-strategy
Select which technology partners a B2B SaaS vendor integrates with and how deep each partnership goes - demand-data partner prioritization (deal-attached revenue, retention lift, competitive necessity), the referral-to-OEM depth ladder with graduation gates, joint-roadmap and co-build governance, certification-program joins with budgeted renewals, sourced-vs-influenced pipeline attribution, and where the technology-partnerships function reports. Use whenever the user mentions integration partner
- Instalaciones / 1h
- 16
- GitHub Stars
- 3
- Actualizado
- 14 oct
kjhk3082skill-update
Use when the user wants to check whether installed agent skills are outdated or update them - "update my skills", "are my skills up to date", "스킬 업데이트", "스킬 최신화" - for skills installed with npx skills, as git clones, or as Claude Code plugins, across Claude Code, Codex, Cursor, Gemini CLI and other agents.
- Instalaciones / 1h
- 15
- GitHub Stars
- 0
- Actualizado
- 2 nov