po-owner
Product Owner Agent. 제품 정책 결정, 요구사항 승인, 우선순위 관리, 비즈니스 목표 정의를 담당합니다. 정책, 승인, 우선순위, PO, 제품 관련 요청 시 사용됩니다.
Install with Tessl CLI
npx tessl i github:shaul1991/shaul-agents-plugin --skill po-owner63
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
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 the Product Owner agent role with clear trigger terms in Korean and explicit 'when to use' guidance. The main weakness is that the capabilities described are somewhat abstract management functions rather than concrete technical actions, and some trigger terms could overlap with other management-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Product Owner) and lists some actions (제품 정책 결정, 요구사항 승인, 우선순위 관리, 비즈니스 목표 정의), but these are somewhat abstract management concepts rather than concrete technical actions. | 2 / 3 |
Completeness | Clearly answers both 'what' (제품 정책 결정, 요구사항 승인, 우선순위 관리, 비즈니스 목표 정의) and 'when' with explicit trigger guidance (정책, 승인, 우선순위, PO, 제품 관련 요청 시 사용됩니다). | 3 / 3 |
Trigger Term Quality | Includes good coverage of natural Korean trigger terms users would say: '정책', '승인', '우선순위', 'PO', '제품'. These are terms users would naturally use when needing product owner assistance. | 3 / 3 |
Distinctiveness Conflict Risk | While 'PO' and '제품' are somewhat specific, terms like '정책', '승인', '우선순위' could overlap with other management or planning skills. The Product Owner role is defined but could conflict with general project management skills. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides useful templates and frameworks for a Product Owner role but lacks clear workflow guidance on when and how to apply them. The content explains concepts Claude likely already knows (MoSCoW, RICE) rather than focusing on project-specific decisions and constraints. Templates would benefit from concrete completed examples rather than empty placeholders.
Suggestions
Add a clear sequential workflow showing when to use each template/framework (e.g., '1. Define business goal → 2. Write user stories → 3. Prioritize with RICE → 4. Get approval')
Replace empty template placeholders with one concrete completed example showing proper usage
Remove explanations of standard frameworks (MoSCoW, RICE definitions) and focus on project-specific rules or customizations
Add validation checkpoints for decision-making (e.g., 'Before approving, verify stakeholder sign-off exists')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably organized but includes some explanatory content that Claude already knows (e.g., basic definitions of MoSCoW, RICE formula explanations). The tables and templates add value but could be more condensed. | 2 / 3 |
Actionability | Provides templates and checklists which are somewhat actionable, but lacks concrete executable examples. The templates are fill-in-the-blank style rather than showing completed examples that demonstrate proper usage. | 2 / 3 |
Workflow Clarity | No clear sequential workflow is defined. The skill lists responsibilities and provides templates but doesn't explain when or how to use them in sequence. Missing validation steps for decision-making processes. | 1 / 3 |
Progressive Disclosure | Content is structured with headers and sections, but everything is inline in one file. The output file locations are mentioned but no references to separate detailed documentation for complex topics like RICE scoring or user story writing. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%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 | |
- 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.