CtrlK
BlogDocsLog inGet started
Tessl Logo

deepep-to-cam-converter

识别代码中可替换为CAM算子的DeepEP算子,基于实际运行参数校验约束,自动完成通信域转换(NCCL->HCCL)、设备适配(CUDA->NPU)及算子替换。

60

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./jiuwenclaw/jiuwenclaw/resources/agent/jiuwenclaw_workspace/skills/deepep-to-cam-converter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, validation-rich migration workflow with excellent sequencing and clean one-level reference disclosure, but it carries redundant restatements of the same rules and leaves the core operator interface mapping abstract in-body.

Suggestions

Consolidate the repeated default-vs-runtime-value and nccl/cuda->hccl/npu rules into a single authoritative statement; have phase self-checks reference it instead of restating it.

Add a short inline dispatch/combine → CAM interface mapping example or a one-line-per-mode table linking directly to the relevant reference section so the central replacement is actionable without leaving SKILL.md.

Tighten 检查清单 so it does not duplicate the per-phase 阻断检查 items verbatim.

DimensionReasoningScore

Conciseness

Mostly efficient operational guidance with tables and checklists, but the same constraints (default vs runtime value, nccl->hccl/cuda->npu, shmem release after sync) are restated across 核心原则, the phase self-checks, and 检查清单, which could be tightened.

2 / 3

Actionability

Strong concrete guidance (exact NCCL->HCCL/CUDA->NPU mapping table, import ordering, npu-smi info, aclshmem_free/finialize), but the central operator interface mapping in 3.2 is left abstract ("映射为对应的CAM接口调用", "根据文档调整参数") and deferred to references rather than shown copy-paste ready.

2 / 3

Workflow Clarity

Four clearly sequenced phases each with an explicit 🛑 阻断检查 self-check block, pass/fail status, and error-recovery feedback loops ("若失败请停止,针对不满足项重新执行"), plus a final checklist — matching the 'clear sequence with explicit validation steps' anchor.

3 / 3

Progressive Disclosure

A 参考文档库 section signals five one-level-deep reference files by topic (通信转换/A2/A3/Shmem/fused deep moe), all of which exist under references/, keeping the body an overview while detail lives in well-organized reference docs.

3 / 3

Total

10

/

12

Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinct, naming several concrete migration actions in a clear niche, but it omits any explicit 'when to use' trigger guidance and relies on technical jargon with limited natural-term variation.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when migrating DeepEP-based MoE code to Ascend NPU or when the user mentions DeepEP/CAM/昇腾 migration.'

Broaden trigger terms with natural user phrasing such as 迁移/migrate, Ascend/昇腾, and MoE/Expert Parallel alongside the technical keywords.

Consider mentioning Ascend/NPU by name in the description so users referencing the target hardware surface the skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "识别...DeepEP算子", "校验约束", "通信域转换(NCCL->HCCL)", "设备适配(CUDA->NPU)", "算子替换" — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

The 'what' is answered with concrete actions, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Uses on-point domain keywords (DeepEP, CAM, NCCL, HCCL, CUDA, NPU) but lacks natural trigger phrasing and common variations a user might say (e.g. 迁移/migrate, Ascend/昇腾, MoE), so it sits at 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

The DeepEP→CAM/Ascend-NPU migration niche with NCCL/HCCL and CUDA/NPU terminology is highly specific and extremely unlikely to trigger the wrong skill.

3 / 3

Total

10

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
XiaoLuoLYG/GOD
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.