Menu
SkillsMP has collected 16 skills from TencentBlueKing/bk-lite. Open a skill to review its source and details.
Showing 16 of 16 collected skills.
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, architecture, data flow, dependency direction, seam placement, maintainability, extensibility, testability, or AI navigability, or when another…
Diagnosis loop for hard, unclear, recurring, cross-module, async/concurrency, data-flow, consistency, and performance bugs. Use when the user asks to diagnose, debug, troubleshoot, or fix a defect whose local fast path lacks a proven cause.
MUST USE when user wants to 调研/research/搜索/search/查/找/look up anything on the internet — e.g. 全网调研 X / 帮我调研一下 X / 查一下 X / 搜搜 X / 看看大家怎么评价 X / X 上有什么讨论 / research this topic。 Also MUST USE when user mentions any platform or shares any URL/链接:…
Source text: Chinese
Use when proposing or reviewing BK-Lite operations-product modules, MVP scope, product specifications, competitor-derived designs, workflow/state models, extensibility decisions, permissions, audit, execution safety, or acceptance criteria.
Review committed or uncommitted changes along two axes — repository standards and the originating capability contract or change spec. Use for a branch, PR, or work-in-progress review.
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
Use only when the user explicitly asks to be grilled on a non-code plan, decision, or design that does not need repository documentation.
Use only when the user explicitly asks for grill-with-docs or asks to grill an ambiguous repository change while maintaining glossary and ADR documentation.
Use when explicitly invoked by the user or delegated by another Grill skill to stress-test a plan, decision, or idea one question at a time.
Use only when the user explicitly invokes implement or asks to execute a durable change spec or ticket set; ordinary clear edits use the repository fast path.
Use only when the user explicitly asks for an architecture-deepening audit, visual report, and follow-up grilling of a selected opportunity.
Use only when the user explicitly asks to install, repair, or reconfigure this repository's Grill engineering workflow, tracker conventions, and domain docs.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Thorough, user-invoked tech debt and architecture audit of the current codebase. Produces TECH_DEBT_AUDIT.md with file-cited findings, severity, effort estimates, and a required "looks bad but is actually fine" section. Use only when the user explicitly asks…
Use only when the user explicitly asks to turn the current, already-aligned conversation into a durable change spec without another interview.
Use only when the user explicitly asks to split an aligned plan or spec into durable tracer-bullet tickets with declared blocking edges.