Loading...
Loading...
Found 9 Skills
Rigor Analyze / Rigor Audit read-only skill for deep learning research repositories. Use when the user wants to read and understand a repository, inspect model structure and training or inference entrypoints, review configs and insertion points, or flag suspicious implementation patterns without modifying code or running heavy jobs. Do not use for active command execution, broad refactoring, speculative code adaptation, or automatic bug fixing.
GitHub 审视 - Read-only GitHub triage for issues and PRs. 触发条件/Triggers: 需要分析 GitHub Issues 或 PRs、生成审查报告、或分类问题。 核心原则/Core Principles: - 只读不写/Read-only: 永不修改 GitHub 状态 - 证据支持/Evidence: 每个结论都需要 GitHub permalink 证明 - 并行分析/Parallel: 每个 Issue/PR 独立后台任务 - 报告输出/Reports: 写入临时目录,不操作 GitHub 命令/Commands: - /审视 analyze <repo> - 分析仓库所有开放 Issue 和 PR - /审视 issues <repo> - 只分析 Issues - /审视 prs <repo> - 只分析 PRs - /审视 <URL> - 分析特定 Issue 或 PR - /analyze <repo> - English command 能力/Capabilities: GitHub 数据读取、问题分类、证据收集、报告生成、后台并行处理。
Collect read-only evidence about PlanetScale org, database, branches, webhooks, backups, roles, Insights, recommendations, and traffic configuration.
User-invoked read-only pass for checking whether the current direction is tunnel-visioned: strip the session's bait, fan out 2 to 5 same-model fresh reads, and report divergence first without treating convergence as proof.
Read-only Runpod spend audit: find idle spend, explain serverless billing when nothing seems to run, break spend down by resource type and by resource, and give a whole-account snapshot. Every figure comes from the MCP billing and list reads; it recommends actions and never stops or changes anything. Use when the user asks about their bill, what is costing money, what is running on the account, or tells you to stop or delete idle resources it did not name by id: the audit with ids and the user's own next steps is the answer. A resource the user names by id goes to pod-doctor or endpoint-ops, and the change is made.
Read-only audit of which tests are missing, weak, stale or mis-scoped, mapped by what tests actually call, ranked P0-P3 by risk, with a verdict and a worklist for awesome-test-writing. Use when asked what tests are missing, where the coverage gaps are, or to audit a test suite.
Read knowledge shipped inside installed dependencies — detect the ecosystem and exact installed version, locate AGENTS.md and guides per the `knowledge.sources` slot, and report doc-versus-code skew. Read-only. Use for "which version is installed", "find the framework's AGENTS.md", "inspect dependency source", "kontekst frameworka".
Check whether the current task's claimed outcome is confirmed.
Investigate a codebase, discover change scope, or diagnose a bug with evidence. Use for read-only surveys, impact analysis, and root-cause work.