pm-analyst

PM Analyst Agent. 비즈니스 분석, 시장 조사, ROI 계산을 담당합니다. 분석, 시장조사, ROI, KPI, 경쟁사 관련 요청 시 사용됩니다.

Quality

52%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/pm-analyst/SKILL.md

Quality

Content

22%

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

This skill reads more like a role description or capability overview than actionable guidance. It lists frameworks and templates Claude already knows without providing project-specific instructions, concrete execution steps, or validation checkpoints. The content would benefit from focusing on what's unique to this project's analysis needs rather than generic PM knowledge.

Suggestions

Replace generic framework definitions (SWOT, Porter's 5 Forces) with project-specific analysis instructions or remove them entirely—Claude knows these concepts

Add concrete workflows: e.g., 'To perform competitor analysis: 1. Run X command, 2. Gather data from Y sources, 3. Output to Z format'

Include executable examples showing how to actually produce an analysis artifact, not just empty templates

Specify validation steps: how to verify analysis quality, what constitutes a complete deliverable, review checkpoints before finalizing reports

Dimension	Reasoning	Score
Conciseness	The content includes useful frameworks and templates but explains concepts Claude already knows (SWOT, Porter's 5 Forces, TAM/SAM/SOM definitions). The KPI tables with generic targets add bulk without project-specific value.	2 / 3
Actionability	The skill describes what an analyst does and lists frameworks but provides no executable guidance. There are no concrete commands, code, or step-by-step instructions for actually performing analyses—just definitions and empty templates.	1 / 3
Workflow Clarity	No clear workflow or sequence is provided. The skill lists categories of work (시장 분석, 사용자 분석, etc.) but doesn't explain how to execute any of them, when to use which framework, or how to validate outputs.	1 / 3
Progressive Disclosure	The content is organized with clear headers and sections, and references output locations. However, it's somewhat monolithic with framework definitions that could be in separate reference files, and lacks links to detailed methodology guides.	2 / 3
	Total	6 / 12 Passed

Description

82%

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

This description effectively communicates both what the skill does and when to use it, with good Korean trigger terms that users would naturally employ. However, the specificity of capabilities could be improved with more concrete actions, and some trigger terms like '분석' are broad enough to potentially cause conflicts with other analytical skills.

Suggestions

Add more specific concrete actions like 'SWOT 분석 작성', '경쟁사 매트릭스 생성', '재무 모델 구축' to improve specificity

Consider adding more distinctive trigger terms that differentiate from general data analysis, such as '사업 타당성', '시장 진입 전략', '투자 수익률'

Dimension	Reasoning	Score
Specificity	Names the domain (business analysis, market research, ROI calculation) and lists some actions, but lacks comprehensive detail about specific concrete actions like 'create competitor matrices' or 'build financial models'.	2 / 3
Completeness	Clearly answers both what ('비즈니스 분석, 시장 조사, ROI 계산을 담당합니다') and when ('분석, 시장조사, ROI, KPI, 경쟁사 관련 요청 시 사용됩니다') with explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes natural Korean keywords users would say: '분석' (analysis), '시장조사' (market research), 'ROI', 'KPI', '경쟁사' (competitor). These are terms users would naturally use when requesting these services.	3 / 3
Distinctiveness Conflict Risk	While PM/business analysis is a defined niche, terms like '분석' (analysis) are quite broad and could overlap with data analysis or other analytical skills. The 'PM Analyst Agent' title helps but the triggers could still conflict.	2 / 3
	Total	10 / 12 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	10 / 11 Passed

Repository: shaul1991/shaul-agents-plugin
Commit: 9242c58

Reviewed: 4 months ago

Table of Contents

Discovery Implementation Validation

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.