Pesquisa e Web

Implements structured usage logging and audit trails for cost and session tracking. Use when adding audit trails, usage analytics, or cost tracking to a skill.

Merges ephemeral report and analysis artifacts into permanent documentation. Use when LLM-generated markdown files have accumulated and need consolidation.

Converts a specification into a phased, dependency-ordered implementation plan. Use after specification is complete and before execution begins.

Searches GitHub for existing implementations, libraries, or patterns. Use when finding code examples or prior art on a topic during a research session.

Applies layered n-tier architecture with enforced boundaries. Use when designing moderate systems needing clear presentation, domain, and persistence layers.

Audit Skill() refs; detect hubs, isolates, and dangling targets. Use when auditing skills.

Refreshes README structure and content using repo context and exemplar research. Use when README needs a structural update after significant project changes.

Audits dependency supply chains for bad versions, lockfile drift, and artifact integrity. Use when adding deps, handling incidents, or releasing a plugin.

Probe memory/summary clarity via dual anchor questions: task progress, info gaps. Use when verifying session state or summary before handoff or compression.

Refines an active research session by drilling deeper into a subtopic. Use after tome:research to narrow results to a specific channel or angle.

Evaluates and improves skills, agents, commands, and hooks after a workflow slice. Use when execution felt slow, confusing, repetitive, or fragile.

Applies data-grid architecture for high-traffic stateful workloads. Use when a single database cannot scale and in-memory partitioning is needed.