Content
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body contains genuinely useful concrete guidance for LinkedIn profile optimization, but it is padded with redundant template boilerplate and its code/CLI examples do not match the actual bundled script. Referenced reference files are missing, so progressive disclosure and actionability both fall short of fully executable.
Suggestions
Make the documented code and CLI match the actual bundle: either implement generate_headline/write_about_section/suggest_keywords/optimize_experiences and the CLI in scripts/main.py, or replace the examples with the real optimize(role, specialty, achievements) API.
Remove the duplicated description restatements and generic boilerplate ('Implementation Details', 'Output Requirements', 'Error Handling', 'Response Template') that Claude already knows, keeping only the concrete formulas, keyword table, and worked examples.
Create the referenced files (references/linkedin-examples.md, keywords-by-specialty.json, headline-templates.md) and move the large keyword table and about-section example into them, or delete the broken references and keep the content inline with accurate paths.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Useful concrete examples (headline formulas, keyword table, about-section structure) are interspersed with large amounts of generic templated boilerplate ('Implementation Details', 'Output Requirements', 'Error Handling', 'Response Template') and verbatim re-statements of the description, so it is mostly efficient but padded rather than lean. | 2 / 3 |
Actionability | Concrete code and CLI examples are provided, but they reference a LinkedInOptimizer API (generate_headline, suggest_keywords, optimize_experiences) and a scripts/linkedin_optimizer.py CLI that do not exist in the actual bundle, whose main.py only exposes optimize(); guidance is therefore incomplete and not executable as written. | 2 / 3 |
Workflow Clarity | A sequenced 5-step Workflow plus a Quality Checklist and Quick Check exist, but the steps are abstract ('Confirm the user objective', 'Validate the request') without concrete validation checkpoints tied to the real script, leaving checkpoints implicit rather than an explicit validate-fix-retry loop. | 2 / 3 |
Progressive Disclosure | The body signals references (references/linkedin-examples.md, keywords-by-specialty.json, headline-templates.md) but none of these files exist in the bundle (only guidelines.md is present), and content that should be split out (keyword table, about example) is inlined, matching the score-2 anchor of structure present but references not resolving and inline content that should be separate. | 2 / 3 |
Total | 8 / 12 Passed |