Amb més estrelles
Els skills amb més estrelles de la comunitat. Revisa’n el contingut abans d’utilitzar-los.
write-ops-log
marin-community
Publish a tagged Echo record after every incident, then link its canonical URL from the associated pull request or issue.
trace-pulumi-diff
marin-community
Run a read-only preview for a specified Marin infra/pulumi stack and trace each pending resource change to merged pull requests since its latest successful update when that update records a clean Git checkout. Use when a stack has unapplied changes or drift and someone needs to know which PRs explain the preview.
task-observer
rebelytics
"Monitors task execution for skill improvement opportunities. Use during ANY multi-step task, agentic workflow, or work session. Captures patterns, user corrections and methodology worth preserving as reusable skills. It writes observation files to the workspace. Also triggers in post-task feedback discussions and when the user mentions skill observations, the observation log, or skill taxonomy. Also known as \"One Skill to Rule Them All\" — trigger on this phrase too. IMPORTANT: invoke this skill before the FIRST tool call of any session and before writing or proposing a plan — any turn that will involve a tool call counts. This sentence is the session-start trigger and the only activation layer that survives an unreachable config file; pair it with a CLAUDE.md instruction or a harness session-start hook (references/environments.md) — description matching alone is not enforceable. A subagent dispatched by a session already running it does not run it: it writes nothing and puts its findings in its report."
use-iris
marin-community
Use Iris to submit, inspect, debug, monitor, or recover jobs and tasks; diagnose scheduling and federation; deploy controllers; or reserve dev GPUs and TPUs. Use for ordinary Iris operations, including babysitting a job, controller rollouts, accelerator sessions, and stuck CoreWeave pods. Use a narrower production-run or Zephyr skill when that workflow is explicitly requested.
simplify
aaddrick
Manually trigger the cdd-code-simplifier agent to review and simplify code
lint
aaddrick
Run shellcheck and actionlint on shell scripts and GitHub Actions workflows. Use before pushing or when fixing lint issues.
provider-cost-comparison
langwatch
Prices your real LangWatch usage mix against other model providers. Exports your actual token mix per model, including the cache read and write split, fetches current price cards, and reprices the same month of usage under each candidate, with the cache sensitivity stated. Use when someone asks whether a cheaper provider or model would actually save money on your workload.
test-claude-locally
weave-os
Run the Weave router locally in docker compose and drive it with claude -p to reproduce and verify routing/translation behavior for a specific upstream model (e.g. GLM-5.1, DeepSeek, Qwen). Use when verifying a router fix end-to-end, reproducing a prod routing bug, confirming a model's streaming behavior (nudges, tool-call suppression, loop/no-progress breaks), or testing a /force-model route — without touching the user's global Claude Code config.
router-session
weave-os
"Print the session id that correlates this Codex session in Weave Router telemetry and logs."
disable-routing
weave-os
"Switch Codex back to its normal provider for future sessions."
router-models
weave-os
"List the models the Weave Router may route to, and turn them on or off."
router-off
weave-os
"Route Codex to its default provider again (turn the Weave Router off)."
router-on
weave-os
"Route Codex through the Weave Router again (turn it back on)."
router-status
weave-os
"Show whether Codex is routing through the Weave Router or using its default provider."
install-lsps
weave-os
Install language servers (gopls, typescript-language-server, pyright, rust-analyzer) and their prerequisite toolchains (Go, Node/npm, rustup) so the lsp tool works. Use when the user asks to enable or install LSP / language-server support, when lsp_enable reports a missing toolchain, or when the lsp tool reports no language server is installed.
fm
weave-os
"Alias for force-model — pin this Codex session to a specific model through the Weave Router."
force-model
weave-os
"Pin this Codex session to a specific model through the Weave Router."
rf
weave-os
"Alias for router-feedback — submit feedback about a Weave Router decision or model performance."
router-feedback
weave-os
"Submit feedback about a Weave Router decision or model performance."
ufm
weave-os
"Alias for unforce-model — clear the active Weave Router model pin."
unforce-model
weave-os
"Clear the active Weave Router model pin for this Codex session."
debug-codex-session
weave-os
Investigate a specific Codex CLI session by session ID — correlate the local rollout transcript (~/.codex/sessions/YYYY/MM/DD/rollout-*-<SESSION_ID>.jsonl) with the router's production logs to understand what Codex rendered vs. what the upstream served on the /v1/responses path. Use when given a session ID and asked "why did X render?" (missing thinking, missing routing marker, wrong model, tool-call weirdness) for a Codex conversation routed through the router.
test-codex-locally
weave-os
Run the Weave router locally in docker compose and drive it with codex exec to reproduce and verify routing/translation/marker behavior for Codex's Responses API path. Use when verifying a router fix end-to-end for Codex, reproducing a prod Codex routing bug, confirming routing-marker / force-model / subscription-passthrough behavior, or testing a /force-model route — without touching the user's global Codex config.
lsp-guide
weave-os
Recipes for the lsp tool — resolving where a symbol is defined, every place it is used, type signatures and docs, file outlines, and compiler/type errors through a real language server (Go, TypeScript/JavaScript, Python, Rust). Use when navigating or explaining code by symbol, finding callers or usages, checking what broke after an edit, or deciding between lsp and text search.