retrieving-knowledge
Retrieves project knowledge resources by browsing categories, searching tags, or filtering by keywords. Use when exploring existing knowledge or finding specific documentation entries.
发现 testing security knowledge base 相关 Skills,比较来源仓库和用途,查看适合你工作流的技能说明。
Retrieves project knowledge resources by browsing categories, searching tags, or filtering by keywords. Use when exploring existing knowledge or finding specific documentation entries.
Systematic documentation review following document-writer principles. Use when user requests documentation review, quality check, or principle compliance verification.
This skill should be used when the user mentions "burn", "tensor", "module", "backend", "training", "ONNX", "autodiff", "deep learning in Rust", or any Burn framework related query. Routes to appropriate domain...
Manage solution outline documents - standards, examples, validation, and deliverable extraction
Test skill with table-format references
Load when you struggled with something docs would have helped, when you're about to move on from a complex area you now understand, or when managing skills
Deeply interviews the user about a bug before investigating or fixing it. Use this when the user says "interview me about [bug]", "I have a bug to report", "let's work on this bug", "found a bug", "there's a bu...
Identifies bugs, analyzes errors, performs root cause analysis, and proposes fixes
Helps organize tasks, create action plans, manage schedules, and track progress
MUST CHECK FIRST before DeepWiki or any external research. Local-first codebase documentation wikis. **Priority order for library/framework research**: 1. deep-codebase-wiki (THIS) - check local wikis FIRST 2....
Use when creating new skills, updating existing skills, or understanding skill structure. Triggers: "create a skill", "write a skill", "new skill for", "skill that does", "how do skills work". Provides complete...
Search the internet using Gemini CLI when web search tools are unavailable or when user requests Gemini specifically.
Guide for creating effective skills. Use when you want to create a new skill (or update an existing skill) that extends an agent with specialized workflows, tool integrations, or repo conventions.
Use for root cause analysis of bugs or issues. Systematically investigates problems to identify underlying causes.
Use to systematically validate documents, stories, or processes against defined checklists. Ensures quality and completeness.
Shared reference documentation for PRISM skills. Contains common best practices, command patterns, and examples used across multiple skills.
Example skill demonstrating the registry structure and format
Categorize and display available skills. Use when listing or selecting skills.
This skill should be used when the user asks about "how to research", "research best practices", "evaluate sources", "source credibility", "academic research", "find reliable information", "cite sources", "rese...
Implements the Zettelkasten method for Obsidian. Use when the user wants to organize, create, link, critique, or visualize notes according to Zettelkasten principles. Supports distilling raw text into atomic no...
Systematic bug investigation and fix workflow. Gathers symptoms, forms hypotheses, investigates root cause, implements fix, and verifies. Use for debugging, fixing errors, or troubleshooting. Triggers: debug, f...
Orchestrate fixing issues found by $review. Handles issue discovery, user confirmation, plan creation, and execution via $implement. Triggers: fix review issues, fix findings, address review feedback.
Conduct structured web research with hypothesis tracking. Synthesizes information from multiple sources into actionable findings. Use for technical research, API docs, best practices. Triggers: web research, lo...
Comprehensive multi-wave web research with strategic source selection. Gathers information from official docs, community resources, and advanced sources. Use for deep technical research, API documentation, best...
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。