CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

personal-planner

为提问者生成个性化的未来规划与建议书。输入提问者的背景信息(职业、年龄、资源、目标、困境等),基于深度画像分析、行业趋势研判和商业洞察,输出一份图文并茂、有数据支撑、逻辑严密的 Markdown 规划报告,保存到项目 markdown/ 目录。触发条件:用户提供个人背景信息并希望获得规划建议,提到"帮我规划"、"未来规划"、"职业规划"、"个人发展"、"我该怎么做"、"给我写一份建议书"、"我的优势是什么"、"下一步怎么走",或者提供了详细个人信息并问 Claude 如何利用好它。即使用户只说"帮我分析一下我的情况"、"我现在很迷茫"但附带了背景信息,也应使用本 skill。

68

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured instruction-only skill: the three-phase workflow is clearly sequenced, guidance is concrete (question bank, report skeleton, file naming, chart rules), and token efficiency is respected via tables. The main gaps are mild redundancy between the profile-format and report-structure sections, no final output-validation step, and a monolithic single file where a question bank / template reference could reduce context load.

Suggestions

Add a final validation pass to 阶段三 (e.g., a checklist confirming every claim cites a data source, core assumptions are listed at the top, and each Top-3 opportunity has a concrete 'first action'), turning the workflow from sequenced to checkpointed.

Merge the 1.2 画像输出格式 block into the 3.1 报告结构 section (or make 1.2 a one-line pointer) to remove the duplicated skeleton and reduce tokens.

Move the profiling question bank (the two dimension tables) and the full report template into references/ files (e.g., references/profiling-questions.md, references/report-template.md), keeping SKILL.md as a lean process overview.

DimensionReasoningScore

Conciseness

The body is dense and table-driven with no padding explaining concepts Claude already knows, but the 1.2 画像输出格式 block substantially restates the 3.1 报告结构 skeleton, and a few lines ('每个主要论点都需要 ✅…') repeat prior sections — anchor 4 rather than 5.

4 / 5

Actionability

Concrete, copy-paste-ready artifacts: an interview question bank with specific probes ('30% 概率 10 倍回报 vs 100% 概率平稳回报'), a full report markdown skeleton, an explicit output path convention, and per-chart-type rules. Some directives remain topical rather than methodical ('市场规模、增速、主要参与者、利润分布' names what to analyze but not how), matching anchor 4.

4 / 5

Workflow Clarity

A clear three-phase sequence (画像构建 → 战略研判 → 报告生成) with an input checkpoint ('不足的维度需主动追问…不要一次问超过 3 个问题') and a deficiency-handling rule with a field priority order. Minor gap: no validation step for the generated report itself (e.g., checking that every module actually has data support and assumptions listed), so it sits at anchor 4 rather than 5.

4 / 5

Progressive Disclosure

No bundle files exist, and the single file is cleanly hierarchical (three phases → numbered subsections → tables) making navigation easy. At ~190 lines, the profiling question bank and the report template are candidates for reference files, which is the minor gap that keeps this at anchor 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Description

91%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 clearly states what the skill produces (a personalized, data-backed Markdown planning report with an explicit save location) and gives an explicit, well-considered trigger list including edge cases. Only minor issues: slight buzzword flavor in a few capability phrases and a couple of over-generic trigger terms.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('生成个性化的未来规划与建议书', '输出…Markdown 规划报告,保存到项目 markdown/ 目录', '基于深度画像分析、行业趋势研判'), though phrases like '商业洞察' lean slightly buzzword, keeping it below anchor 5.

4 / 5

Completeness

Explicitly answers both 'what' (generate a personalized data-backed Markdown planning report saved to markdown/) and 'when' via a dedicated '触发条件:' clause with concrete trigger phrases, matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases users would actually say ('帮我规划', '未来规划', '职业规划', '我该怎么做', '我的优势是什么', '下一步怎么走'), including low-signal variants like '我现在很迷茫' with the background-info qualifier.

5 / 5

Distinctiveness Conflict Risk

The personal-planning report niche is distinct and triggers are anchored to background-info requests, but broadly applicable phrases like '我该怎么做' and '下一步怎么走' create minor overlap risk with general advice or career-coaching skills.

4 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

digoal/blog

Path

skills/skills_for_claude_web/personal-planner/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.