RADAR DE SKILLS · GITHUB
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
- 15.652
- repositorios
- 2532
- última sincronización
- 13 oct 2026
pandoscopeto-tickets
Break a plan, spec, or the current conversation into tracer-bullet tickets with blocking edges, published to the project tracker. Use when splitting approved work into issues.
- instalaciones
- 5
- GitHub Stars
- 1
- Actualizado
- 23 sept
pandoscopewriting-adrs
Format, numbering, and when-to-write criteria for Architecture Decision Records in docs/adr/. Use when recording an architectural decision, when another skill flags a decision as ADR-worthy, or when the user asks to write or review an ADR.
- instalaciones
- 5
- GitHub Stars
- 1
- Actualizado
- 23 sept
decebalsclean-code
Clean Code principles (DRY, KISS, YAGNI), naming, function design and readability. Use when code is hard to read, with long methods, unclear names, duplication or deep nesting. For how responsibilities are split across classes and which way dependencies point, use solid-principles instead.
- instalaciones
- 5
- GitHub Stars
- 743
- Actualizado
- 6 sept
earthtojakecad-viewer
Start CAD Viewer and return review links for CAD and robot-description files. Use when visually reviewing .step, .stp, .glb, .stl, .3mf, .dxf, .urdf, .srdf, or .sdf files, especially when handed off from CAD, URDF, SRDF, or SDF generation skills.
- instalaciones
- 5
- GitHub Stars
- 16,1 mil
- Actualizado
- 18 sept
greptileaigreploop
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments. Triggers Greptile review, fixes all actionable comments, pushes/re-shelves, re-triggers review, and repeats. Use when the user wants to fully optimize a PR/MR/CL against Greptile's code review standards.
- instalaciones
- 5
- GitHub Stars
- 402
- Actualizado
- 11 sept
joelhookseffect-ts
Write idiomatic Effect v4 TypeScript following official best practices from effect-solutions and the Effect source. Use when writing, reviewing, or refactoring Effect code: services (ServiceMap.Service), layers and dependency injection, error handling (Schema.TaggedErrorClass), data modeling (Schema.Class, branded types, variants), testing (@effect/vitest), HTTP clients (effect/unstable/http), CLI tools (effect/unstable/cli), config, observability, and project setup. Triggers on: 'Effect', 'effe
- instalaciones
- 5
- GitHub Stars
- 43
- Actualizado
- 20 may
appeekyandroid-aso
When the user wants to optimize their Google Play Store listing — title, short description, full description, keywords, ratings, or Play Store-specific features. Use when the user mentions "Google Play", "Android", "Play Store", "Play Console", "short description", "full description indexed", "Google Play ASO", or wants Google Play-specific keyword, creative, or ratings strategy. For iOS App Store optimization, see aso-audit and metadata-optimization.
- instalaciones
- 5
- GitHub Stars
- 1,9 mil
- Actualizado
- 22 ago
appeekycompetitor-analysis
When the user wants to analyze competitors' App Store strategy, find keyword gaps, or understand competitive positioning. Also use when the user mentions "competitor analysis", "competitive research", "keyword gap", "what are my competitors doing", or "compare my app to". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.
- instalaciones
- 5
- GitHub Stars
- 1,9 mil
- Actualizado
- 22 ago
appeekykeyword-research
When the user wants to discover, evaluate, or prioritize App Store keywords. Also use when the user mentions "keyword research", "find keywords", "search volume", "keyword difficulty", "keyword ideas", or "what keywords should I target". For implementing keywords into metadata, see metadata-optimization. For auditing current keyword performance, see aso-audit.
- instalaciones
- 5
- GitHub Stars
- 1,9 mil
- Actualizado
- 22 ago
appeekymetadata-optimization
When the user wants to optimize App Store metadata — title, subtitle, keyword field, or description. Also use when the user mentions "optimize my title", "ASO metadata", "keyword field", "character limits", "app description", or "write my subtitle". For keyword discovery, see keyword-research. For full ASO audits, see aso-audit.
- instalaciones
- 5
- GitHub Stars
- 1,9 mil
- Actualizado
- 22 ago
appeekyonboarding-optimization
When the user wants to improve their app's onboarding experience, increase activation rate, reduce Day 1 drop-off, or optimize the first-run flow. Use when the user mentions "onboarding", "first-run", "activation", "tutorial", "day 1 retention", "new user flow", "permission prompts", "sign-up conversion", "onboarding funnel", or "users dropping off early". For overall retention strategy, see retention-optimization. For paywall placement, see monetization-strategy.
- instalaciones
- 5
- GitHub Stars
- 1,9 mil
- Actualizado
- 22 ago
appeekyscreenshot-optimization
When the user wants to design, optimize, or evaluate App Store screenshots and preview videos. Also use when the user mentions "screenshots", "app preview", "product page design", "screenshot design", "creative assets", or "what should my screenshots show". For A/B testing screenshots, see ab-test-store-listing. For full ASO audit, see aso-audit.
- instalaciones
- 5
- GitHub Stars
- 1,9 mil
- Actualizado
- 22 ago
appeekyseasonal-aso
When the user wants to optimize their App Store listing for seasonal events, holidays, or trending moments — including keyword opportunities, metadata updates, screenshot theming, and timing strategy. Use when the user mentions "seasonal", "holiday", "Christmas", "New Year", "Valentine's Day", "summer", "back to school", "seasonal keywords", "trending now", "limited time", or wants to capitalize on a calendar event. For general keyword research, see keyword-research. For full metadata rewrites,
- instalaciones
- 5
- GitHub Stars
- 1,9 mil
- Actualizado
- 22 ago
lvlup-swbody-too-long
A skill with a body that exceeds the word limit.
- instalaciones
- 5
- GitHub Stars
- 28
- Actualizado
- 18 sept
lvlup-swbroken-reference
A skill with a broken reference link.
- instalaciones
- 5
- GitHub Stars
- 28
- Actualizado
- 18 sept
lvlup-swcheckpoint
Save and mutate workflow state — init a workflow, update fields, transition phases, and capture a structured handoff before context exhaustion. Use when the user says 'save progress', 'checkpoint', 'I need to stop', or runs /checkpoint. Writes current workflow phase, task progress, and artifacts to the event store for later resumption. Do NOT use for restoring/reading state after a session break (that is /rehydrate) or for workflow initialization framing handled by ideate/debug/refactor commands
- instalaciones
- 5
- GitHub Stars
- 28
- Actualizado
- 18 sept
lvlup-swcleanup
Post-merge workflow resolution. Verifies PR merge status, backfills synthesis metadata, force-resolves review statuses, transitions to completed, and cleans up worktrees/branches. Use when the user says 'cleanup', 'resolve workflow', 'mark as done', or runs /cleanup. Do NOT use before PRs are merged.
- instalaciones
- 5
- GitHub Stars
- 28
- Actualizado
- 18 sept
lvlup-swdebug
Bug investigation and fix workflow. Triggers: 'debug', 'fix bug', 'investigate issue', 'something is broken', or /debug. Hotfix track for quick fixes, thorough track for root cause analysis. Do NOT use for feature development or refactoring. Do NOT escalate to /ideate unless the fix requires architectural redesign.
- instalaciones
- 5
- GitHub Stars
- 28
- Actualizado
- 18 sept
lvlup-swdiscover
Research and discovery workflow for document deliverables — competitive analyses, architecture comparisons, ADR scaffolding, literature reviews, vendor evaluations. No TDD requirement. Phases: gathering → synthesizing → completed. Triggers: 'discover', 'research', 'explore topic', or discover.
- instalaciones
- 5
- GitHub Stars
- 28
- Actualizado
- 18 sept
lvlup-swdogfood
Review failed Exarchos MCP tool calls from the current session, diagnose root causes, and categorize into code bug, documentation issue, or user error. Use when the user says 'dogfood', 'review failures', 'what went wrong', 'triage errors', or runs /dogfood. Scopes exclusively to Exarchos tools (exarchosworkflow, exarchosevent, exarchosorchestrate, exarchosview, exarchossync). Do NOT use for debugging application code or non-Exarchos tool failures.
- instalaciones
- 5
- GitHub Stars
- 28
- Actualizado
- 18 sept
lvlup-swgit-worktrees
Git worktree management for parallel agent team development. Triggers: 'create worktree', 'worktree setup', or during /delegate dispatch. Do NOT use for branch creation without delegation context.
- instalaciones
- 5
- GitHub Stars
- 28
- Actualizado
- 18 sept
lvlup-swinvariants
Guided authoring of an architectural invariant catalog entry through a 6-step interview (elicit, locate, weight, enforce, number, commit). Drives the invariantsscaffold, invariantsadd and invariantsamend orchestrate verbs — the agent supplies judgment and natural-language elicitation; the verbs own schema validation, file writing, and event emission. Correcting an existing entry is invariantsamend (id-targeted, field-scoped), never a re-run of invariantsadd. Defaults to mode: audit; mode: check
- instalaciones
- 5
- GitHub Stars
- 28
- Actualizado
- 18 sept
lvlup-swmerge-orchestrator
The composed executor that lands a subagent worktree branch onto an integration branch with preflight + recorded recovery point. For a shared integration branch route through serializemerge (the single-writer lease that composes this action); invoke mergeorchestrate directly only for a non-integration merge or when you already hold the lease. Triggers: operator (or nextactions) surfaces the merge verb via Exarchos MCP. Local git operation — NOT remote PR merging (that is mergepr).
- instalaciones
- 5
- GitHub Stars
- 28
- Actualizado
- 18 sept
lvlup-swmutation-adequacy
Verification-ladder R5 review dimension: the mutation-adequacy adequacy backstop. Runs the diff-scoped mutation gate, reads the carrier, and turns surviving / NoCoverage mutants into concrete 'write a test that kills : ' follow-ups. Triggers: 'mutation adequacy', 'check mutation score', or /review on a HIGH-tier feature. The mutation SCORE is advisory by default (a config override is needed to block on it). The NoCoverage axis has its own real, functioning block-mode enforcement path under revie
- instalaciones
- 5
- GitHub Stars
- 28
- Actualizado
- 18 sept