CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hybrid-mode-management

混合模式项目管理。基于愿景驱动 (OBM) + 价值蓝图 (Value Blueprint) + 流动执行 (Flow) 的项目管理方法。能力价值化,通过蓝图量化能力价值。包含周决策会议、愿景对齐检查、优先级计算、价值评估等功能。触发场景:(1) 周决策会议 (2) 功能愿景对齐检查 (3) 事项优先级排序 (4) AI 效率追踪 (5) 能力价值评估。

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 ./docs/99-archive/old-docs/hybrid-mode-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%Weight 40%Scale 1-5

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

The body contains genuinely actionable methodology (formulas, scoring anchors, thresholds, templates) but is severely undermined by wholesale duplication of the v1.0 content after the v2.0 content, creating contradictory guidance (能力成熟度 vs 价值蓝图), stale dated state, and a bloated monolithic file with no bundle references. It needs a de-duplication pass and extraction of templates/metrics into reference files.

Suggestions

Delete the appended v1.0 sections (lines ~484-737): the duplicate '使用指南', '愿景对齐检查', '优先级计算', 'AI 效率指标', '能力成熟度模型', '流动执行', template, FAQ, and '相关资源' blocks directly contradict the v2.0 '价值蓝图替代能力成熟度' framing and roughly double the token cost.

Move the weekly meeting template, value blueprint template, and AI-efficiency metrics tables into references/ files linked one level deep, keeping SKILL.md as a lean overview with the formulas and decision thresholds.

Remove hardcoded time-sensitive state (e.g., '当前状态 (2026-03-21)', '本周新增:+0.330', '价值等级: 成长期') and replace it with instructions for computing current state, or move it to an explicitly dated report file.

Fix the relative links (../../docs/...) to point at files inside the skill bundle, or remove them if those documents are not shipped with the skill.

DimensionReasoningScore

Conciseness

The 730-line body is heavily padded: the entire v1.0 content is appended after the v2.0 content, duplicating '使用指南', '愿景对齐检查', '优先级计算', 'AI 效率指标', '流动执行', the meeting template, FAQ, and '相关资源' nearly verbatim, and it also explains concepts Claude already knows (generic L1-L5 capability maturity levels, basic PM notions). This matches the 'severely verbose; heavily padded' anchor; it is not a 2 because the duplication goes well beyond 'several unnecessary padded sections' — roughly half the file is redundant. Hardcoded time-sensitive state ('当前状态 (2026-03-21)', '本周新增:+0.330') further bloats it without being in a deprecated section.

1 / 5

Actionability

Concrete, usable guidance is present throughout: an exact priority formula with weights ('优先级 = 愿景×0.5 + 价值×0.3 + (1-难度)×0.15 + AI 辅助×0.05'), a defined value formula with 0-1 scoring anchors, decision thresholds (≥0.8 立即执行 / <0.4 放弃), and a copy-paste-ready 45-minute meeting template with time boxes. It is not a 5 because examples use placeholder rows ('事项 1') whose stated results don't fully check out against the formula, and the duplicated/conflicting sections leave ambiguity about which guidance is current; it is above 3 because the instruction-only guidance is specific and directly executable.

4 / 5

Workflow Clarity

Multi-step processes are sequenced (能力识别 → 价值量化 → 价值可视化 → 价值分配; 周决策会议 → 确定 Top 3 → 每日执行 → 周回顾) with decision thresholds acting as partial checkpoints. It is capped at 3 because validation is only implicit (no step to verify computed scores or reconcile the contradictory v1.0 '能力成熟度模型' section with the v2.0 '价值蓝图替代能力成熟度' section), and the wholesale duplication of the workflow sections makes the canonical sequence genuinely ambiguous.

3 / 5

Progressive Disclosure

There is real structure (clear emoji-headed sections, a '相关资源' section with links), but the skill ships no references/, scripts/, or assets/ files: every template, metrics table, and FAQ is inlined in one 730-line monolith, and the '相关资源' links point to ../../docs/ paths outside the bundle (../../docs/VISION_ALIGNMENT_CHECKLIST.md, ../../docs/meetings/weekly/TEMPLATE.md) rather than one-level-deep bundle files. This matches the 'some structure but content that should be separate is inline' anchor; it is not a 2 because section headers and clearly-labeled links do exist, and not a 4 because the meeting templates and metric tables clearly belong in separate reference files.

3 / 5

Total

11

/

20

Passed

Description

83%Weight 40%Scale 1-5

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

A strong description: it names the domain, enumerates four-plus concrete functions, and provides an explicit five-item trigger scenario list, cleanly answering both what and when. Minor room to improve via natural synonym coverage and reducing internal jargon (OBM/Value Blueprint) in favor of user-spoken phrasing.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities — "包含周决策会议、愿景对齐检查、优先级计算、价值评估等功能" (weekly decision meetings, vision alignment checks, priority calculation, value assessment) — which matches the 'several specific actions with minor gaps' anchor. It is not a 5 because the actions are only named, not elaborated, and phrases like "能力价值化,通过蓝图量化能力价值" lean abstract; it is above 3 because more than 1-2 concrete actions are explicitly enumerated.

4 / 5

Completeness

It explicitly answers both 'what' ("基于愿景驱动 (OBM) + 价值蓝图 (Value Blueprint) + 流动执行 (Flow) 的项目管理方法") and 'when' with five concrete trigger scenarios, matching the top anchor of clear what + explicit when with concrete trigger phrases. It is not a 4 because the when-clause is already fully explicit rather than merely implied or generic.

5 / 5

Trigger Term Quality

The explicit trigger list "触发场景:(1) 周决策会议 (2) 功能愿景对齐检查 (3) 事项优先级排序 (4) AI 效率追踪 (5) 能力价值评估" covers good natural keywords a user of this methodology would say. It falls short of 5 because common synonyms/variations (e.g., 排期/任务排序, 价值量化, sprint/周会) are missing and some framing terms (OBM, Value Blueprint, Flow) are internal jargon rather than user-spoken phrases.

4 / 5

Distinctiveness Conflict Risk

The hybrid-mode methodology framing and its specific triggers (vision alignment check, AI efficiency tracking, capability value assessment) carve out a mostly distinct niche with only minor overlap risk against generic project-management or planning skills. It is not a 5 because "项目管理" is a broad domain and terms like 优先级排序 could overlap with generic prioritization/scheduling skills.

4 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (738 lines); consider splitting into references/ and linking

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 9 suspicious

Warning

Total

13

/

16

Passed

Repository

Fractal-Holographic-Lab/holo

Path

docs/99-archive/old-docs/hybrid-mode-skill/SKILL.md

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.