studio-operations
Expert operations manager specializing in day-to-day studio efficiency, process optimization, and resource coordination. Focused on ensuring smooth operations, maintaining productivity standards, and supporting all teams with the tools and processes needed for success.
24
6%
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-operations/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 generic job posting for an operations manager rather than a functional skill description. It lacks any concrete actions, natural trigger terms, or explicit guidance on when Claude should select this skill. The use of first/third person framing as 'Expert operations manager' is more of a persona description than a capability description.
Suggestions
Replace vague buzzwords with specific concrete actions (e.g., 'Creates project schedules, tracks resource allocation across teams, identifies workflow bottlenecks, generates status reports').
Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks about scheduling, workflow issues, team capacity, operational bottlenecks, or studio resource planning').
Define the specific domain more narrowly to reduce conflict risk — what kind of studio? What specific processes? What tools or outputs does this skill produce?
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like 'studio efficiency', 'process optimization', 'resource coordination', and 'maintaining productivity standards' without listing any concrete actions. No specific tasks are described. | 1 / 3 |
Completeness | The 'what' is extremely vague (no concrete actions), and there is no 'when' clause or explicit trigger guidance whatsoever. It reads like a job description rather than a skill description. | 1 / 3 |
Trigger Term Quality | The description contains corporate buzzwords ('process optimization', 'resource coordination', 'productivity standards') rather than natural keywords a user would actually say when needing help. No actionable trigger terms are present. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so generic ('operations', 'process optimization', 'supporting all teams') that it could overlap with virtually any organizational or management-related skill. Nothing distinguishes it from other skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
12%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a persona/personality definition rather than an actionable skill document. It spends most of its token budget on abstract identity descriptions, communication style guidance, success metrics, and generic management concepts that Claude already understands. It lacks any concrete, executable instructions, specific tools, real examples, or meaningful references to external resources.
Suggestions
Replace abstract descriptions with concrete, executable guidance—specify actual tools (e.g., specific project management software, scripting commands, automation platforms) and provide real examples of process optimization rather than generic templates with placeholder brackets.
Cut at least 60% of the content by removing personality traits, communication style examples, success metrics, and 'advanced capabilities' sections that describe general management concepts Claude already knows.
Add specific, actionable workflows with validation steps—for example, a concrete SOP for a real studio operation (equipment checkout, vendor onboarding, incident response) with actual commands or tool-specific instructions.
Create separate reference files for templates and detailed methodologies, and link to them from a concise overview in the main skill file to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive sections that describe abstract qualities, personality traits, communication styles, and success metrics that Claude doesn't need explained. The content is heavily padded with motivational language, emoji headers, and generic operations management concepts that add no actionable value. | 1 / 3 |
Actionability | Despite its length, the skill provides no concrete, executable guidance. There are no specific commands, tools, scripts, or real-world examples. The templates are generic placeholders with bracketed fill-in-the-blank fields, and the 'procedures' are abstract descriptions like 'Analyze current operational workflows' without any specifics on how. | 1 / 3 |
Workflow Clarity | There is a 4-step workflow process with a logical sequence (Assessment → Coordination → Implementation → Monitoring), and the SOP template includes quality checks and escalation steps. However, the steps are entirely abstract with no validation checkpoints, no concrete actions, and no feedback loops for error recovery. | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files for detailed guidance. The final line vaguely references 'core training' and 'comprehensive process frameworks' without any actual links or file references. Everything is dumped inline with no clear navigation structure for discovery. | 1 / 3 |
Total | 5 / 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.