Showing 33811–33840 of 49371 skills
创建新的钉钉技能(dingtalk skill)。当用户提到"创建新技能"、"新建技能"、"开发钉钉技能"、"新增钉钉功能"、"添加钉钉接口支持"、"我需要一个钉钉 xxx 技能"、"钉钉待办"、"钉钉签到"、"钉钉考勤"、"钉钉审批"、"钉钉日程"等希望将某个钉钉 API 领域封装成可复用 skill 时,必须使用此技能。此技能包含完整的技能创建流程:SDK 探索 → SDK Python 测试 → 纯 HTTP Python 测试(两步全通过)→ SKILL.md 编写。测试未全部通过不得创建 skill。
breath57/dingtalk-skills
钉钉待办管理。当用户提到"钉钉待办"、"待办任务"、"创建待办"、"新增待办"、"查看待办"、"完成待办"、"标记完成"、"删除待办"、"待办列表"、"我的待办"、"设置截止时间"、"指派待办"、"dingtalk todo"、"todo task"、"task management"时使用此技能。支持:创建待办(含描述/截止时间/优先级/参与者)、获取详情、查询列表(按完成状态过滤)、更新待办、标记完成、删除待办等全部待办类操作。
breath57/dingtalk-skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
breath57/dingtalk-skills
Default silent entry for questions, research, artifacts, code, coordination and persistent projects. When available to the host, infer the relevant evidence path from each direct request, including real-world, pre-build engineering, or linked hybrid research; choose proportionate Light-to-Ultra workflow depth and load only relevant guidance. Keep the host-selected default model unless the user or host explicitly changes it. The direct user phrase “调用我的 workflow skills” explicitly selects this workflow.
zy839971925-zyy/Agent--deep-research-Workflow-Skills
Use when a material result needs contract verification, independent or orthogonal review, evaluator-validity checks, effectiveness review, or defensible closure.
zy839971925-zyy/Agent--deep-research-Workflow-Skills
Use when the deliverable is a choice, recommendation, prioritization, trade-off, resource allocation, or robustness-sensitive decision.
zy839971925-zyy/Agent--deep-research-Workflow-Skills
Use when a scenario calls for real-world evidence, pre-build engineering/architecture research, or a linked hybrid; infer the route without requiring the user to label it. Keep the host-selected default model; infer proportionate workflow depth, honoring explicit depth requests such as Ultra.
zy839971925-zyy/Agent--deep-research-Workflow-Skills
Use when work creates durable artifacts or external side effects, delegates execution, needs authorization, or must preserve state/checkpoint/recovery semantics.
zy839971925-zyy/Agent--deep-research-Workflow-Skills
Use when a task needs problem framing, representation choice, decomposition, relationships, causal chains, hypotheses, or careful interpretation.
zy839971925-zyy/Agent--deep-research-Workflow-Skills
Implement a feature phase by phase from a phased JSON master or Markdown plan. Before each phase, confirm whether to create/run unit tests and whether to run ck:quality, unless explicit flags supply those choices. Supports token-budgeted execution, resumable state, and TDD handoff to ck:test.
DangQuangSE/team-development-skills
Create a machine-readable phased JSON plan bundle from a spec or feature description. Produces a compact master manifest plus per-phase step files for resumable ck:cook execution.
DangQuangSE/team-development-skills
Independent senior-engineering quality auditor — architecture, ownership, domain integrity, abstraction, and maintainability. Use as `--gate` inside the ck:cook pipeline (blocks a phase on BLOCKER/HIGH/current-change MEDIUM findings) or call directly with `--audit`, `--diff`, `--changed` on any repository, directory, or file. Never writes tests and never edits production code — it returns structured findings only; ck:cook or ck:fix apply the fix.
DangQuangSE/team-development-skills
Standalone testing skill — owns writing and running tests, verifying behavior, and two-pass TDD orchestration. Default mode analyzes changed scope and runs the relevant tests; `--unit`/`--integration`/`--e2e`/`--all` scope by test type; `--verify` reruns exactly the prior failures; `--all-phases <plan>` sweeps every completed phase for regression. `--tdd --prepare`/`--tdd --verify` bracket `ck:cook` for red-green TDD. Never edits production code, and blocks until a phase's `ck:quality` gate is APPROVED (except `--tdd --prepare`, which runs before any implementation exists).
DangQuangSE/team-development-skills
Dispatch to the right problem-solving technique based on how you're stuck
DangQuangSE/team-development-skills
Phase 1 of the SRS workflow. User gives a project topic → AI runs a deep, categorized brainstorm (5 mandatory rounds) to fully understand actors, features, scope boundary, tech constraints, and business rules before writing anything.
DangQuangSE/team-development-skills
Phase 6 of the SRS workflow. Reads approved plan files and generates a complete IEEE 830-compliant SRS — one file per section, no word limit. A full SRS may span 300+ pages across all files.
DangQuangSE/team-development-skills
Phase 8 of the SRS workflow. Generates an improvement report covering deferred features, technical risks, validation warnings, and next-version candidates. No word limit.
DangQuangSE/team-development-skills
Phase 4 of the SRS workflow. Reads spec.md and writes one detailed plan file per SRS section (§1–§3 + Appendices). Each file is a complete blueprint for the corresponding SRS section. No word limit.
DangQuangSE/team-development-skills
Phase 9 of the SRS workflow. Saves all project context to _context/ files so future Claude sessions can resume without re-reading the full SRS.
DangQuangSE/team-development-skills
Phase 2 of the SRS workflow. Reads projects/{slug}/brainstorm.md and writes a comprehensive spec.md. No word limit.
DangQuangSE/team-development-skills
Phase 7 of the SRS workflow. Runs srs_validator.py --dir on the generated SRS files, reports errors and warnings, auto-fixes ERRORs, and outputs a COMPLIANT / PARTIALLY COMPLIANT / NON-COMPLIANT verdict.
DangQuangSE/team-development-skills
Generate IEEE 830 SRS from raw requirements. Use when the user says "write SRS", "generate requirements doc", "analyze requirements", "I have raw requirements from a client", or pastes a client email/chat/PRD.
DangQuangSE/team-development-skills
Full SRS workflow: Brainstorm → Spec → Plan (per-section files) → User Review → SRS Generation → Validation → Improvement Report → Context Save. Use when user provides a project topic and wants a complete requirements pipeline.
DangQuangSE/team-development-skills
Implement a feature phase by phase from a phased JSON master or Markdown plan. Before each phase, confirm whether to create/run unit tests and whether to run ck:quality, unless explicit flags supply those choices. Supports token-budgeted execution, resumable state, and TDD handoff to ck:test.
DangQuangSE/team-development-skills
Create a machine-readable phased JSON plan bundle from a spec or feature description. Produces a compact master manifest plus per-phase step files for resumable ck:cook execution.
DangQuangSE/team-development-skills
Independent senior-engineering quality auditor — architecture, ownership, domain integrity, abstraction, and maintainability. Use as `--gate` inside the ck:cook pipeline (blocks a phase on BLOCKER/HIGH/current-change MEDIUM findings) or call directly with `--audit`, `--diff`, `--changed` on any repository, directory, or file. Never writes tests and never edits production code — it returns structured findings only; ck:cook or ck:fix apply the fix.
DangQuangSE/team-development-skills
Standalone testing skill — owns writing and running tests, verifying behavior, and two-pass TDD orchestration. Default mode analyzes changed scope and runs the relevant tests; `--unit`/`--integration`/`--e2e`/`--all` scope by test type; `--verify` reruns exactly the prior failures; `--all-phases <plan>` sweeps every completed phase for regression. `--tdd --prepare`/`--tdd --verify` bracket `ck:cook` for red-green TDD. Never edits production code, and blocks until a phase's `ck:quality` gate is APPROVED (except `--tdd --prepare`, which runs before any implementation exists).
DangQuangSE/team-development-skills
Design, implement, migrate, debug, review, and test ReactiveUI 24+ applications. USE FOR: ReactiveObject; WhenAnyValue; ObservableAsPropertyHelper/ToProperty; ReactiveCommand; WhenActivated; Bind/OneWayBind/BindCommand; Interaction; routing and view location; RxAppBuilder; source generators; ReactiveUI.Primitives vs *.Reactive distributions; schedulers; DynamicData; validation; WPF, Avalonia, MAUI, WinUI, WinForms, Blazor. DO NOT USE FOR: generic Rx.NET pipelines without MVVM (use dotnet-rx); unrelated MVVM frameworks; visual UI design.
NetFabric/intelligentium
Design, implement, debug, test, and review in-process producer-consumer pipelines with System.Threading.Channels. USE FOR: Channel<T>, ChannelReader<T>, ChannelWriter<T>, bounded/unbounded queues, BoundedChannelFullMode, backpressure, TryWrite, WriteAsync, ReadAsync, ReadAllAsync, completion, cancellation, concurrent producers/consumers, BackgroundService workers, in-memory event queues, overload protection, and channel performance. DO NOT USE FOR: durable or cross-process messaging, distributed pub/sub, broker delivery guarantees, Rx.NET stream composition, task-parallel dataflow blocks, or simple thread-safe collections with no asynchronous producer-consumer requirement.
NetFabric/intelligentium
Build, maintain, debug, and review Visual Studio Code extensions. Use when: extension manifest, activation, commands, views, tree views, webviews, notifications, settings, language providers, tasks, debuggers, custom editors, authentication, Accounts, sign-in, account management, session lifecycle, Workspace Trust, desktop or web compatibility, testing, CI, packaging, Marketplace publishing. DO NOT USE FOR: general web applications or Copilot agent customization; use the relevant web-development or agent-authoring guidance.
NetFabric/intelligentium