CtrlK
BlogDocsLog inGet started
Tessl Logo

enterprise-planner

为企业生成深度未来规划与建议书。输入企业名称、简介、网站等基本信息,自动搜索企业相关情报、行业数据、竞争格局,构建完整企业画像,再结合当下环境与未来趋势,输出图文并茂、有数据支撑的战略规划报告(Markdown 格式),保存到当前项目的 markdown/ 目录。触发条件:用户提供企业信息并希望获得规划建议、提到"企业规划"、"帮这家公司规划"、"战略建议书"、"商业计划"、"给XX公司写规划"、"公司未来怎么走"、"帮我分析一下这家企业"。即使用户只说"帮我给这家公司写个规划"但附带了企业信息,也应使用本 skill。

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

A thorough, well-structured instruction skill with concrete search templates, diagram syntax rules, and output conventions. The main weaknesses are the absence of explicit validation checkpoints in the workflow and a monolithic single-file layout that inlines reference material rather than splitting it out.

Suggestions

Add an explicit validation/verification checkpoint between research and report writing (e.g., 'before drafting, confirm each core claim has a cited source; if not, re-search or mark as 推演') to strengthen the feedback loop.

Move the detailed Mermaid rendering rules and the report-opening template into a separate reference file (e.g. references/report-format.md) and link to it from SKILL.md to improve progressive disclosure.

Tighten the conciseness of the Mermaid rules section by consolidating the four chart-type examples into a compact do/don't checklist.

DimensionReasoningScore

Conciseness

Largely efficient and assumes Claude's competence — it does not explain what mermaid or SWOT is — though the mermaid rendering rules and report template could be tightened slightly.

4 / 5

Actionability

Provides concrete, executable guidance: ready-to-use search query strings, mermaid code blocks with enforced formatting rules, filename format examples, and a report-opening template; minor gaps as it is instruction-only without shell-runnable code.

4 / 5

Workflow Clarity

A clear five-step sequence (信息采集 → 画像 → 环境分析 → 规划撰写 → 输出) with required report sections and an information-insufficiency fallback, but lacks an explicit validate→fix→retry checkpoint within the research-to-report loop.

4 / 5

Progressive Disclosure

Well-organized with clear section headers, but everything is inlined in a single ~278-line SKILL.md with no bundle files; substantial reference-style content (mermaid rules, report template) that could live in separate reference files is kept inline.

3 / 5

Total

15

/

20

Passed

Description

95%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, detailed description that clearly states capability, output artifact, and trigger conditions with natural user phrasing. Slight specificity ceiling because the description describes the pipeline at a high level rather than enumerating every report sub-action.

DimensionReasoningScore

Specificity

Lists several concrete actions — '搜索企业相关情报、行业数据、竞争格局', '构建完整企业画像', '输出...战略规划报告', '保存到当前项目的 markdown/ 目录' — with only minor gaps in enumerating sub-actions.

4 / 5

Completeness

Explicitly answers both 'what' (generates data-backed strategic planning reports in Markdown) and 'when' (concrete trigger phrases plus an edge-case rule for ambiguous invocations with attached enterprise info).

5 / 5

Trigger Term Quality

Comprehensive coverage of natural user phrases including synonyms — '企业规划', '帮这家公司规划', '战略建议书', '商业计划', '给XX公司写规划', '公司未来怎么走', '帮我分析一下这家企业'.

5 / 5

Distinctiveness Conflict Risk

Clear niche — enterprise future-planning advisory reports — with distinctive triggers and minimal overlap risk against other skills.

5 / 5

Total

19

/

20

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
digoal/blog
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.