Menu
Refresh all project knowledge skills by re-reading the codebase, docs, and source files to update stale SKILL.md content.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
SignalDB Tempo API compatibility - implemented/stub endpoints, query flow, admin API, Grafana native plugin, and built-in Tempo datasource support. Use when working with HTTP API, Grafana integration, or query endpoints.
SignalDB architecture reference - FDAP stack, write/query data flow, service components, deployment models, and dual catalog system. Use when understanding how components fit together, data flow, or system design.
SignalDB crate map - workspace members, module locations within common/writer/querier/router crates, and key root files. Use when navigating the codebase, finding where code lives, or understanding module boundaries.
SignalDB multi-tenancy and authentication - tenant model, auth flow, isolation layers, slug-based naming, API keys, admin API, and CLI. Use when working with tenant isolation, authentication, API keys, or dataset management.
SignalDB configuration reference - all TOML sections, environment variables, database/discovery/storage/WAL/schema/auth/queue settings, and service ports. Use when working with configuration, environment variables, or TOML settings.
Step-by-step guide for adding a new signal type or table to SignalDB - schema definition, Flight schema, OTLP conversion, WAL operation, acceptor/writer/querier/router updates, and testing. Use when adding new signal types, metric types, or tables.
| name | refresh-skills |
| description | Refresh all project knowledge skills by re-reading the codebase, docs, and source files to update stale SKILL.md content. |
| disable-model-invocation | true |
Scan the codebase and update all knowledge skills in .claude/skills/ with current information.
For each skill listed below, read the source-of-truth files, compare against the current SKILL.md content, and update anything that is stale, missing, or incorrect. Preserve the YAML frontmatter (name, description, user-invocable, disable-model-invocation) but update the description if the scope changed.
Do NOT rewrite skills that are already accurate. Only touch what changed.
Each knowledge skill declares its source-of-truth files in the sources: list
of its own frontmatter — read that list, not a central table. Additional notes:
Cargo.toml (workspace members), read src/*/src/lib.rs
or src/*/src/main.rs for each crate to check module structuresources:; cross-reference with the
architecture, flight-schemas, and storage-layout skills for consistencydocs/architecture/overview.mdCargo.tomlschemas.toml (new fields, new versions, new signal types)src/common/src/config/mod.rsCargo.tomlAfter refreshing, print a summary like:
Skills refresh complete:
- architecture: updated (added new Querier port, updated deployment notes)
- storage-layout: up to date
- flight-schemas: updated (new log schema v2 fields)
- ...