position-product
Define product positioning and brand strategy
Install with Tessl CLI
npx tessl i github:jpoutrin/product-forge --skill position-product39
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
22%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 is too brief and abstract to effectively guide skill selection. It lacks concrete actions, explicit trigger conditions, and sufficient keyword coverage. The description would benefit significantly from specifying deliverables and adding a 'Use when...' clause.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about brand positioning, competitive differentiation, value propositions, or market positioning strategy'
List specific concrete actions such as 'Creates positioning statements, develops brand messaging frameworks, analyzes competitive positioning, defines target audience personas'
Include natural keyword variations users might say: 'branding', 'market position', 'differentiation', 'brand identity', 'messaging strategy'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language ('define', 'positioning', 'strategy') without listing any concrete actions. It doesn't specify what outputs are produced or what specific tasks are performed. | 1 / 3 |
Completeness | Only weakly addresses 'what' with vague terms and completely lacks any 'when' guidance or 'Use when...' clause. There are no explicit triggers for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant domain keywords ('product positioning', 'brand strategy') that users might say, but lacks common variations like 'branding', 'market positioning', 'competitive positioning', 'brand identity', or 'value proposition'. | 2 / 3 |
Distinctiveness Conflict Risk | The terms 'positioning' and 'brand strategy' provide some domain specificity, but could overlap with marketing, messaging, or general business strategy skills. Not distinct enough to avoid conflicts. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions primarily as a redirect to an external file rather than providing actionable guidance itself. It lacks concrete examples, executable code, and the actual discovery questions or process steps. The content would be significantly improved by either inlining the key process elements or providing a meaningful overview with examples.
Suggestions
Include the actual discovery questions or at least representative examples directly in the skill content rather than requiring a file read
Add a concrete JSON schema example showing the expected output format for discovery-results
Provide validation steps to verify the source file exists and the output was saved correctly
Include at least one complete example of the interactive flow (sample question, sample answer, resulting JSON)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some redundancy - the execution instructions and source content location sections largely repeat the same information about reading from the source file. | 2 / 3 |
Actionability | The skill provides vague direction rather than concrete guidance. It tells Claude to 'follow the documented process exactly' but the actual process is in an external file not shown here. No executable code, specific commands, or examples of the discovery questions are provided. | 1 / 3 |
Workflow Clarity | Steps are listed (read file, extract questions, run Q&A, save results) but lack validation checkpoints. There's no guidance on error handling, what format the JSON should be, or how to verify the process completed correctly. | 2 / 3 |
Progressive Disclosure | The skill is essentially a pointer to another file with no substantive content of its own. This creates an unnecessary indirection - the skill should either contain the process or provide meaningful overview content, not just redirect entirely. | 1 / 3 |
Total | 6 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | 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.