Amb més estrelles
Els skills amb més estrelles de la comunitat. Revisa’n el contingut abans d’utilitzar-los.
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.
fix-pr-reviews
weave-os
Fetches feedback from a GitHub PR — review-thread comments, ad-hoc PR comments (including those posted as a review's body without a thread), and bot/advisory review submissions — and fixes all of them as they appear (comments before CI). Bot comment-length nits apply verbatim; comments requiring a genuine human decision are NOT auto-fixed and are escalated to the user with options grounded in existing patterns and best practices. After each fix batch, runs pre-commit validation and submits, then waits for CI only when no actionable feedback remains. Loops until all feedback is resolved AND all CI checks have completed. Use when asked to fix PR comments, address review feedback, address PR-level bot reviews (e.g. workweave-bot advisory nits), babysit a PR to merge-ready, or handle review comments.
debug-claude-session
weave-os
Investigate a specific Claude Code session by session ID — correlate the local transcript (~/.claude/projects/...jsonl) with the router's production logs to understand what the client rendered vs. what the upstream served. Use when given a session ID and asked "why did X render?" for a Claude Code conversation routed through the router.
epic-permissions
epicweb-dev
Guide on RBAC system and permissions for Epic Stack
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.
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.
code-context
rajnandan1
Persistent code architecture documentation via a .codecontext/ folder.
experiments
langwatch
Create and run LangWatch experiments for pre-deployment batch testing. Use when the user wants to test an agent against a dataset, compare prompts or models, benchmark quality, detect regressions, or add a CI quality gate. Do not use for production monitoring or guardrails.
debug-instrumentation
langwatch
Debug and improve your LangWatch traces. Inspects production traces for missing input/output, disconnected spans, unlabeled traces, and missing metadata. Use when traces look broken or incomplete.