dbvc
22 verified skills46 total stars
dbx-software-plan-first-showhand
Manual trigger only. Use only when the user explicitly names `dbx-software-plan-first-showhand`, `$dbx-software-plan-first-showhand`, or asks to manually trigger this exact DBX Software Plan-First safe automatic execution phase. Do not auto-trigger for ordinary automatic execution, do-it-all, showhand, or plan-first requests.
testing3
dbx-software-plan-first-implement-feature
Manual trigger only. Use only when the user explicitly names `dbx-software-plan-first-implement-feature`, `$dbx-software-plan-first-implement-feature`, or asks to manually trigger this exact DBX Software Plan-First review-gated single-task implementation phase. Do not auto-trigger for ordinary implementation, tasks.md, next-task, or plan-first requests.
testing3
dbx-software-plan-first-ground-plan
Manual trigger only. Use only when the user explicitly names `dbx-software-plan-first-ground-plan`, `$dbx-software-plan-first-ground-plan`, or asks to manually trigger this exact DBX Software Plan-First read-only grounding phase. Do not auto-trigger for ordinary repo reading, fact checking, plan writing, or implementation requests.
testing3
dbx-product-judgment-control
Use when the user asks to judge whether a product, feature, PRD, information architecture, content, interaction, UI flow, live product, implementation, roadmap, or competitor position is right, good, usable, valuable, coherent, worth building, or product-ready. Grounds judgment in target user, job/context, evidence, alternatives, critical path, trust, and implementation alignment. Ask blocking questions or collect evidence before judging when background is missing. Do not use for pure implementation, generic UI inspiration, ordinary code review without product judgment, generic market summaries, or unsupported guesses.
development3
dbx-software-plan-first-plan-issue
Manual trigger only. Use only when the user explicitly names `dbx-software-plan-first-plan-issue`, `$dbx-software-plan-first-plan-issue`, or asks to manually trigger this exact DBX Software Plan-First plan convergence phase. Do not auto-trigger for ordinary planning, Plan mode, repository exploration, or implementation requests.
testing3
dbx-software-plan-first-finalize-plan
Manual trigger only. Use only when the user explicitly names `dbx-software-plan-first-finalize-plan`, `$dbx-software-plan-first-finalize-plan`, or asks to manually trigger this exact DBX Software Plan-First plan finalization phase. Do not auto-trigger for ordinary plan writing, finalize, seal, or implementation requests.
testing3
dbx-attention-control
Use when the user wants a reusable attention-allocation controller for mixed inbox items, saved content, tasks, ideas, signals, courses, tools, notes, or external-system metadata. Routes each item by stable attention states, grounded in visible evidence and a user-approved profile. Use high-risk prompts only to guard or safety-stop direct action requests. Do not use for ordinary summarization, one-off recommendations, product-specific automation by default, or silent external writes.
tools2
dbx-work-commit-pr
用中文生成或评审工作场景的 commit message 与 PR 描述。适用于用户请求根据最终 diff、 staged changes、working tree changes 或指定 commit 生成 `M-xxx(type): title` commit， 以及中文合同式 PR 四块结构。只以最终变更集为事实边界，忽略聊天过程、失败尝试、 被否决方案和临时调试。不要用于公开开源英文 PR、普通代码 review、实现任务或泛泛解释 commit 概念。
databases2
dbx-goal-writer
Use when the user wants to create, refine, start, or audit an OpenAI Codex goal contract for coding work, especially long-running or validation-heavy tasks. Produces copy-pasteable /goal commands, optional GOAL.md files, and only for large or strict tasks a goal package directory with plan, acceptance, validation, and status files. Do not implement the coding task unless explicitly asked.
development2
dbx-conversation-align
Diagnose communication intent, disagreement layer, correction timing, boundary needs, and response strategy for relationship, work, and conflict conversations.
databases2
dbx-linus-review
Strict pragmatic, evidence-driven technical review for code changes, architecture plans, data models, and implementation proposals. Use when the user explicitly requests Linus-style review, harsh/strict review, pragmatic critique, over-engineering judgment, merge/readiness judgment, or asks whether a technical plan or code change is good enough. Shares judgment principles with dbx-diff-review-control but uses a stricter artifact-agnostic critique loop. Do not use for ordinary code explanation, implementation-only requests, generic encouragement, interpersonal judgment, or normal diff review unless strict/pragmatic critique is explicitly requested.
development2
dbx-skill-portfolio-auditor
Manual-only skill. Use only when the user explicitly names `$dbx-skill-portfolio-auditor`, asks to manually trigger this skill, or launches it from the skill UI. Audits installed or repository agent skills to decide global vs repo/project vs explicit-only vs disable/uninstall. Do not implicitly invoke for generic skill audit, context-bloat, stale-skill, or cleanup requests; ask whether to run this skill instead. Do not use for creating a new task skill; use dbx-skill-architect for skill design.
testing2
dbx-decision-framing
当用户面对高影响、不确定、有真实行动后果的决策，需要在多个选项或 go/no-go 之间取舍时使用。适用于职业去留、技术架构、产品方向、团队组织、生活迁移、投资框架等。先做门禁，再决定 full_decision、quick_decision、clarification、direct_answer 或 safety_redirect。不要用于单纯概念解释、翻译润色、机械代码、一次性写作、低风险日常小事或没有行动后果的泛泛分析。
development2
dbx-skill-architect
Use to create, critique, improve, evaluate, or triage reusable agent skills from recurring scenarios. Enforces fail-closed gates, ASCT control-surface mapping, placement decisions, dominant failure-mode analysis, domain substance discovery, patch-first improvement hypotheses, runner-compatible evals, and artifact validation. Do not use for one-off writing, generic summarization, unsafe surveillance, or doing the user's direct task instead of designing a skill.
testing2
dbx-agent-handoff
Use only when the user wants to hand off the current AI agent session state to another AI agent or a future AI session, including context compaction, restart packets, resume notes, or "下个 session/agent 继续". For ambiguous "handoff/交接文档" requests, use only to ask one clarification question and stop. Do not use for human-facing workplace handoff documents, onboarding docs, project transition memos, status reports, meeting summaries, or general summaries.
testing2
dbx-subagent-context-control
Codex 专用的 subagent 上下文控制辅助技能。Use when 用户要求使用 Codex subagent delegation、Codex worker/explorer delegation、并行 review、独立 reviewer、隔离上下文、不要带上下文、fork_context=false，或把 review/dbx-linus-review/waza-check/plan-eng-review 等技能交给 Codex subagent 执行时。默认新开 Codex subagent 不继承父线程历史，只传最小任务摘要；只有用户明确要求继承父线程时才使用 fork_context=true。不要因为用户讨论业务代码里的 worker、browser worker、架构 explorer 概念而触发。
development2
dbx-open-source-commit-pr
Generate or review concise English commit messages and PR descriptions for public or open-source repositories. Use when the user asks for commit text, PR body, release-style change summary, or validation wording based on a final diff, staged changes, working tree changes, or a specific commit. Do not use for internal M-xxx work PR contracts, generic code review, or explanations of what commits are.
development2
dbx-diff-review-control
High-signal code change review controller for PRs, patches, staged/index changes, working-tree diffs, commit ranges, and file-scoped review. Use when the user asks to review concrete code changes for functional/user-impact risks, data model correctness, state ownership, compatibility, or maintainability. Handles partial staged hunks and user-selected files/commits by selecting the exact review target before reading the diff. Do not use for implementation-only requests, generic code explanation, release publishing, issue triage, or plan-only Linus-style strict-pragmatic critique; for strict critique of a concrete diff, use this skill only to establish the target before dbx-linus-review.
development2
linus-tech-review
Linus Torvalds 风格的技术方案评估与代码评审。仅在用户明确要求 Linus 式 review 或明确要求严苛评估代码改动/技术方案时使用（如"review 改动/代码""评估方案是否合适""检查提交标准""linus-tech-review"）。
tools1
open-source-commit-pr
Generate English commit messages and PR descriptions for public or open-source repositories. Use when the user asks to write, rewrite, or review a commit message or PR body for staged changes, working tree diffs, a specific patch, or a recent commit. Base the output on the final diff and changed files, not on conversational history, abandoned approaches, or internal company process details.
testing1
scenario-skill-architect
Converts recurring scenarios into rigorous agent skill packages through fail-closed gates, IR, mode/route/operation contracts, domain discovery, domain substance gates, failure-knowledge extraction, content-quality rubrics, runner evals, and artifact validation. Use for scenario-first skill creation, critique, patch-first improvement, eval design, triage, and domain-skill discovery. Do not use for one-off writing, generic summarization, unsafe surveillance, or direct tasks. 中文：从重复场景设计/评审 skill；领域型 skill 必须先挖出领域变量、踩坑知识、数据策略和专家质量标准。
development1
commit-pr-contract
用中文生成 commit message（title + body）与 PR 描述，明确区分"长期证据/可追溯性"的 commit 视角和"帮助 reviewer 理解与评审"的 PR 视角。适用于用户请求"写 commit message/写 PR 描述/根据改动生成 commit+PR"，并需遵守 `M-xxx(type): title` 格式与合同式 PR 四块结构；仅以用户提供的最终 diff、指定 commit、staged changes 或 working tree changes 作为内容边界，忽略聊天中的讨论过程、失败尝试、被否决方案与临时调试；可基于最终代码差异推断风险与评审关注点，不足时再询问。
tools1