Pesquisa e Web
5.875 skills encontradas
Alerta por categoria
Receba novas skills de Pesquisa e Web toda segunda
Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.
stack-push
Pushes all branches in a stack and opens or updates one dependent PR per slice. Use after stack-create to publish the stack or after adding commits to a slice.
review-chamber
Captures and retrieves PR-review findings in memory palaces. Use after PR review to store architectural decisions, patterns, and standards for future reference.
tiered-audit
Runs a three-tier codebase audit (git history, targeted scans, full review) with gating. Use when auditing a codebase before release or after incidents.
escalation-governance
Assess whether to escalate models. Use when evaluating reasoning depth.
session-palace-builder
Builds session-scoped temporary memory palaces for extended conversations. Use when tracking state across interruptions in a multi-step project.
content-sanitization
Provides sanitization guidelines for external content in skills and hooks. Use when loading GitHub Issues, PRs, WebFetch results, or any untrusted input.
service-registry
Registers external services with health checks, central config, and unified execution. Use when integrating multiple external services needing coordination.
discourse
Scans HN, Lobsters, Reddit, and tech blogs for community experience reports. Use when gathering practitioner opinions on a technology or approach.
git-platform
Detects git forge (GitHub/GitLab/Bitbucket) and maps CLI commands cross-platform. Use when writing skills that must run on any git hosting provider.
triz
Applies TRIZ cross-domain analogical reasoning to find solutions from adjacent fields. Use when stuck on a problem and needing inventive perspectives.
palace-diagram
Generates Mermaid and ASCII diagrams of palace structure, knowledge topology, and synapse connectivity. Use when inspecting or presenting a palace visually.
architecture-paradigm-service-based
Applies coarse-grained service architecture for deployment independence. Use when independent deployment is needed but shared databases rule out microservices.