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.662
- repositorios
- 3481
- última sincronización
- 31 oct 2026
sylphxaiproduce-product-assets
Produce finished product media and design assets from a current brief and product truth. Use for screenshots, key art, store media, campaign visuals, motion, audio, localization, and accessible variants. Do not use for engine-ready game sprites or tilesets.
- Instalaciones / 1h
- 1
- GitHub Stars
- 2
- Actualizado
- 3 oct
sylphxaiprototype-product
Run the cheapest real probe that can change a product decision, then kill, continue, or pivot from the observation. Use when the user wants a prototype, spike, or cheap test. A demo without a decision criterion is not this job. Do not use to register a production experiment or to polish an already accepted product.
- Instalaciones / 1h
- 1
- GitHub Stars
- 2
- Actualizado
- 3 oct
sylphxaiprovision-agent-workspace
Create or attach an isolated filesystem and shell for an agent — host workspace, sandbox, or VM — with explicit network, secret, lifetime, and cost bounds. Use when the user asks to provision a sandbox, code-execution environment, or throwaway VM. Do not use to write application features in an existing repo.
- Instalaciones / 1h
- 1
- GitHub Stars
- 2
- Actualizado
- 3 oct
sylphxairecord-structured-deliberation
Structure a multi-participant deliberation and record a decision-ready result — options, strongest reasons, dissent, and the named owner's next action. Use when several perspectives, competing proposals, or material objections need a fair synthesis. Do not use for a single-analyst critique or a domain go/no-go review.
- Instalaciones / 1h
- 1
- GitHub Stars
- 2
- Actualizado
- 3 oct
sylphxairesolve-customer-support-case
Resolve one customer support case through a truthful outcome, authorized action, and verified closure. Use for a single ticket, not for designing the support system.
- Instalaciones / 1h
- 1
- GitHub Stars
- 2
- Actualizado
- 3 oct
sylphxairun-product-feedback-loop
Cluster support tickets, in-app feedback, and authorized store reviews into owned product work and close the loop with the people who wrote in. Use when triaging feedback, mining reviews, or asking what customers said after a launch. Do not use to answer one ticket.
- Instalaciones / 1h
- 1
- GitHub Stars
- 2
- Actualizado
- 3 oct
sylphxaiselect-next-work
Select and claim the next high-value work item from current product and repository state. Use when the user wants the agent to choose from an existing backlog. Do not use to finish an already accepted objective.
- Instalaciones / 1h
- 1
- GitHub Stars
- 2
- Actualizado
- 3 oct
sylphxaiui-flow
Design or implement one product UI flow with loading, empty, error, and success states, verified on a real render. Use when the user asks to build a screen, fix a form, design a flow, or match an existing design system. Do not use to review an existing flow, extract a design system, or produce store screenshots.
- Instalaciones / 1h
- 1
- GitHub Stars
- 2
- Actualizado
- 3 oct
zzcigitea
Operate a Gitea instance via its REST API at /api/v1/... with curl. FORCED ROUTING — use this skill for any repository whose git remote host is not github.com: derive the candidate HTTPS base URL from the remote host, probe /api/v1/version, then call the REST endpoints directly.
- Instalaciones / 1h
- 1
- GitHub Stars
- 2
- Actualizado
- 13 oct
crontapcrontap-recurring-agent-endpoint
Schedule an HTTP endpoint that a deployed application uses to start its own agent workflow, then monitor completion with a heartbeat. Use when a user has an application-owned agent runtime that needs a durable external clock.
- Instalaciones / 1h
- 1
- GitHub Stars
- 1
- Actualizado
- 16 sept
crontapcrontap-replace-github-actions-cron
Replace a GitHub Actions schedule trigger with a Crontap HTTP dispatch while keeping the workflow, runner, and logs on GitHub. Use when a user needs a timezone-aware external clock or wants to avoid scheduled-workflow drift.
- Instalaciones / 1h
- 1
- GitHub Stars
- 1
- Actualizado
- 16 sept
crontapcrontap-retries-and-idempotency
Configure Crontap retry policy safely and design scheduled endpoints so repeated requests do not duplicate side effects. Use when a user needs reliable delivery, exponential backoff, or help diagnosing duplicate work.
- Instalaciones / 1h
- 1
- GitHub Stars
- 1
- Actualizado
- 16 sept
crontapcrontap-uptime-monitor
Create and operate a Crontap uptime monitor, tune its failure threshold, pause it during deployments, and inspect probe evidence. Use when a user wants availability checks and down or recovery alerts for an HTTP endpoint.
- Instalaciones / 1h
- 1
- GitHub Stars
- 1
- Actualizado
- 16 sept
replicas-groupreplicas-agent
Guide for background coding agents running inside Replicas cloud workspaces
- Instalaciones / 1h
- 1
- GitHub Stars
- 1
- Actualizado
- 8 sept
fandhe-aicreate-html-report
分析・比較・調査結果・進捗・計画を、意思決定しやすい自己完結 HTML レポートとして生成する。 「HTML レポート作って」「レポートにまとめて」「比較を可視化」「グラフで見せて」「ガントチャート作って」 「ダッシュボード風にまとめて」「見やすくまとめて」で使用。 データと伝えたい関係に応じて KPI・表・bar・line・scatter・heatmap・waterfall・donut・radar・gantt から適切な表現を選び、アクセシブル・レスポンシブ・印刷対応の単一 HTML ファイルを生成する。
- Instalaciones / 1h
- 1
- GitHub Stars
- 0
- Actualizado
- 14 oct
golden-frijolesrefine
The front door for any new ask — feature, bug, spike, or chore. Use when the product owner has a raw idea in their head (or a seed in Roadmap/00-ideas/seeds) and wants to turn it into shippable, sliced work. Runs orientation → appetite → classification → "can we already do this?" → disambiguation → platform-first reframe → slicing, lands a Definition- of-Ready pitch in 00-ideas/seeds, and on approval funds the bet, scaffolds + commits the epic + sprint docs and emits the builder kickoff — epic-m
- Instalaciones / 1h
- 1
- GitHub Stars
- 0
- Actualizado
- 13 oct
golden-frijolesreport
Posts a project report to a chat destination, at the cadence asked for. Daily: a delta-only standup of overnight signals across every repo the project spans (opened/merged PRs and CI, the latest browser smoke, BUILD-ORDER drift, open-PR state, stale previews). Weekly: an executive recap/retro (merged PRs, shipped epics, deploys per app repo, a retro digest). PMO: the weekly operational report with scrum/DORA/doc-ops metrics and a story deck, or the on-demand monthly stakeholder packet with a met
- Instalaciones / 1h
- 1
- GitHub Stars
- 0
- Actualizado
- 13 oct
golden-frijolessmoke
Verifies real, rendered behavior on this project's frontend (local/preview/staging/prod, unauthed or authed) via a real headless-Chromium Playwright browser — the DEFAULT way to check "does this render correctly / does this look right / is this actually live" for any coding agent, not just Claude Code. Use when asked to "smoke test", "verify the live/prod page", "check if X actually rendered", "run a browser smoke", "does this look right on preview", "verify an authed role's flow", or as a post-
- Instalaciones / 1h
- 1
- GitHub Stars
- 0
- Actualizado
- 13 oct
jmbhkimdiagram-design
Create branded architecture, architecture delta, IT current-state, flowchart, sequence, state machine, ER/data model, timeline, swimlane, quadrant, radar/spider, polar chart (polar/radial lollipop), loop/flywheel, nested, tree, org chart, layer stack, exploded axonometric, axonometric plan, Venn, pyramid/funnel, treemap and marimekko, heatmap, bar and dumbbell, waterfall, line (slopegraph, ridgeline, streamgraph, bump), Gantt and scatter charts (bubble, beeswarm), high-level, process, medallion,
- Instalaciones / 1h
- 1
- GitHub Stars
- 0
- Actualizado
- 13 oct
koruworksclose-roadmap
Close out a finished roadmap or feature execution by retiring its planning docs into canonical documentation and carrying what is still owed into the next roadmap — you are the archivist and the architect of the next round, not the coder. Use when the user invokes /close-roadmap , or asks to clean up a feature's docs, retire a roadmap, prepare for the next roadmap, or tidy docs/ / after execute-roadmap or build-feature has finished. Reviews ACCEPTANCE.md check by check, triages every item of ROA
- Instalaciones / 1h
- 1
- GitHub Stars
- 0
- Actualizado
- 13 oct
koruworksdraft-experience
Shape a feature as a product before anyone plans how to build it — the sentence, the ladder of use cases smallest to largest, what stays hidden, and the open product questions. Use when the user invokes /draft-experience , asks what a feature should be, asks whether something is simple enough, or wants the experience document that a technical design, roadmap or plan is then written from. Also use to check an existing feature, bug or proposal against the product shape it claims to serve. Writes d
- Instalaciones / 1h
- 1
- GitHub Stars
- 0
- Actualizado
- 13 oct
koruworksdraft-technical
Design how a feature is built as an engineering conversation with the user before any plan document exists — discover the architecture together, find what the codebase already has to build on, challenge complexity, record every decision with its reason, and write docs/ /TECHNICAL.rev1.md only when the user says the design is ready. Use when the user invokes /draft-technical , or asks to design, architect, or think through how to build a feature, subsystem, integration, migration or infrastructur
- Instalaciones / 1h
- 1
- GitHub Stars
- 0
- Actualizado
- 13 oct
koruworksexecute-plan
Execute a signed-off PLAN.final.md for a single feature yourself, phase by phase, on the current branch — you are the engineer, not a delivery lead. Use when the user invokes /execute-plan, or asks to implement, build or continue an approved plan that is small enough for one person, e.g. "/execute-plan spell-check", "/execute-plan spell-check p1-p3", "build the rest of the plan while I sleep". Resolves the requested phases against the final doc, builds each as its own verified increment, runs it
- Instalaciones / 1h
- 1
- GitHub Stars
- 0
- Actualizado
- 13 oct
koruworksexecute-roadmap
Execute an approved roadmap or plan by orchestrating sub-agents — in parallel, in isolated checkouts, where the runtime allows — you are the delivery lead, not the coder. Use when the user invokes /execute-roadmap, or asks to implement, execute, or oversee an approved roadmap or plan after draft-roadmap or build-feature has produced a signed-off final doc, e.g. "/execute-roadmap implement m2, plans 3.1-3.4, parallelize" or "oversee the roadmap until it is complete". Resolves the requested scope
- Instalaciones / 1h
- 1
- GitHub Stars
- 0
- Actualizado
- 13 oct