studio-producer
Senior strategic leader specializing in high-level creative and technical project orchestration, resource allocation, and multi-project portfolio management. Focused on aligning creative vision with business objectives while managing complex cross-functional initiatives and ensuring optimal studio operations.
19
0%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./pm-studio-producer/skills/SKILL.mdQuality
Discovery
0%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 reads like a job title or LinkedIn summary rather than a functional skill description. It is entirely composed of abstract corporate language with no concrete actions, no trigger terms users would naturally use, and no guidance on when Claude should select this skill. It fails on all dimensions of the rubric.
Suggestions
Replace abstract role descriptions with concrete actions Claude performs, e.g., 'Creates project timelines, allocates team resources across multiple projects, tracks milestones and deliverables, generates status reports.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about project planning, resource scheduling, managing multiple projects, tracking deadlines, or coordinating cross-team work.'
Remove corporate buzzwords like 'orchestration,' 'cross-functional initiatives,' and 'aligning creative vision with business objectives' and replace with specific, actionable language describing what the skill actually does.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses abstract, buzzword-heavy language like 'project orchestration,' 'resource allocation,' 'aligning creative vision with business objectives' without listing any concrete actions Claude would perform. No specific tasks like 'creates project plans,' 'assigns resources,' or 'generates reports' are mentioned. | 1 / 3 |
Completeness | The description vaguely addresses 'what' through abstract role descriptions but never answers 'when should Claude use this skill.' There is no 'Use when...' clause or any explicit trigger guidance, and even the 'what' is too vague to be actionable. | 1 / 3 |
Trigger Term Quality | The description is filled with corporate jargon ('cross-functional initiatives,' 'portfolio management,' 'studio operations') that users are unlikely to naturally say when requesting help. There are no natural trigger terms a user would type in a prompt. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic and could overlap with any project management, leadership, strategy, or operations-related skill. Terms like 'resource allocation' and 'cross-functional initiatives' are so broad they would conflict with many other skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill file reads as an elaborate persona description and job posting rather than actionable instructions for Claude. It is extremely verbose, entirely abstract, and provides no concrete tools, commands, code, or executable workflows. The templates are placeholder-heavy and the workflow steps are strategic platitudes without any operational specificity.
Suggestions
Replace abstract strategic descriptions with concrete, actionable procedures—e.g., specific frameworks for calculating portfolio ROI, actual spreadsheet formulas, or decision trees for resource allocation.
Remove personality/identity sections, communication style examples, and 'learning & memory' sections that describe traits rather than instruct behavior—Claude doesn't need a job description.
Add concrete validation checkpoints to the workflow, such as specific criteria for when a portfolio plan is ready for stakeholder review, or checklists for risk assessment completeness.
Either provide real, filled-in template examples showing expected output quality, or link to separate reference files for detailed templates rather than embedding large placeholder blocks inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive sections describing personality traits, communication style, memory patterns, and success metrics that Claude doesn't need explained. The content is heavily padded with motivational language, emoji headers, and abstract strategic concepts rather than actionable instructions. Much of this reads like a job description rather than a skill file. | 1 / 3 |
Actionability | The skill contains no concrete, executable guidance—no specific commands, code, tools, or step-by-step procedures. The templates are placeholder-heavy markdown with bracketed fill-in-the-blank fields. Workflow steps are abstract strategic descriptions ('Analyze market opportunities') rather than actionable instructions Claude can execute. | 1 / 3 |
Workflow Clarity | The four-step workflow is entirely abstract and lacks any validation checkpoints, decision criteria, or concrete sequencing. Steps like 'Strategic Planning and Vision Setting' contain only vague bullet points with no clear inputs, outputs, or verification mechanisms. There are no feedback loops or error recovery paths. | 1 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files for detailed guidance. The final line vaguely mentions 'core training' and 'comprehensive portfolio management frameworks' without any actual file references. All content is inline with no meaningful structure for navigation or discovery. | 1 / 3 |
Total | 4 / 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 | |
- Repository
- OpenRoster-ai/awesome-openroster
- Commit
09aef5d
- 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.