Generates project-specific stakeholder skills with frontmatter templates, trigger-optimized descriptions, and structures for teams, objectives, and decision patterns.
From skills-toolkitnpx claudepluginhub youngleadersdottech/young-leaders-tech-marketplace --plugin skills-toolkitThis skill is limited to using the following tools:
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
This template guides the creation of project-specific stakeholder skills. Replace all [PLACEHOLDER] values with actual project information.
---
name: [project]-[domain]-stakeholders
description: Stakeholder context for [PROJECT_NAME] [DOMAIN] when discussing [USE_CASE_1], [USE_CASE_2], or [USE_CASE_3]. Auto-invoke when user mentions [PROJECT_TRIGGER], [DOMAIN_TRIGGER], or [TEAM_TRIGGER]. Do NOT load for general [DOMAIN] discussions unrelated to [PROJECT_NAME].
allowed-tools: []
version: 1.0.0
category: Stakeholders
tags: [[project], [domain], [key-theme-1], [key-theme-2]]
last-updated: [YYYY-MM-DD]
---
Description Engineering Guidance:
✅ DO include specific trigger terms:
❌ DON'T use generic descriptions:
Example Good Description:
Stakeholder context for Phoenix UX research project when discussing user testing, research synthesis, or design validation. Auto-invoke when user mentions Phoenix, UX research stakeholders, or design team collaboration. Do NOT load for general UX discussions unrelated to Phoenix.
[TEAM_NAME] Team[PRIMARY_OBJECTIVE_1] (quantified if possible: >95% accuracy, <100ms latency)[PRIMARY_OBJECTIVE_2][PRIMARY_OBJECTIVE_3][ROLE_TITLE] (Use role, not individual name - NO PII)
[SPECIFIC_DECISIONS_THIS_ROLE_MAKES][PREFERRED_CHANNELS_AND_STYLE]
[QUANTIFIABLE_METRICS_THIS_ROLE_CARES_ABOUT]
[CURRENT_CHALLENGE_1] (quantified if possible)[CURRENT_CHALLENGE_2][CURRENT_CHALLENGE_3][DECISION_TYPE]: [APPROVAL_PROCESS_AND_CRITERIA]
[FREQUENCY_AND_FORMAT]
[WHEN_AND_HOW_TO_ESCALATE]
[ROLE_1] → [ROLE_2] → [ROLE_3] (for [DECISION_SCOPE])[SLACK_CHANNEL_OR_EMAIL_GROUP][RECURRING_MEETING_SCHEDULE][CONFLUENCE_WIKI_OR_DOC_LOCATION][EMERGENCY_CONTACT_METHOD] (NO personal phone numbers)Before finalizing skill, verify:
Content Quality:
[PLACEHOLDERS] replaced with actual valuesDescription Engineering:
[LIST_TEST_QUERIES][LIST_TEST_QUERIES]Metadata & Tracking:
allowed-tools: [] set (stakeholder skills are read-only reference)Security & Scope:
.claude/skills/projects/[name]/)Creating New Stakeholder Skill:
User: "Create a stakeholder skill for the Phoenix UX research team"
Claude: [Loads this template skill, uses structure to create Phoenix-specific skill]
Finding Template for Reference:
User: "What's the standard format for stakeholder skills?"
Claude: [Loads this template skill, shows structure and best practices]
Do NOT Use This Template For:
Template Source: Research report + eval committee consensus Template Version: 1.0.0 Last Updated: 2025-10-19 Validation: Ready for Week 1 PoC testing