Agent Skills: skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
ID: MacHu-GWU/sanhe-claude-code-plugins/skill-creator
Install this agent skill to your local
Skill Files
The files that make up skill-creator.
Loading file tree…
More agent skills
- axiom-validate-screenshotsUse when the user mentions App Store screenshot validation, screenshot review, checking screenshots before submission, or verifying screenshot dimensions and content.
- ha-quality-scale-verifyVerifies that a Home Assistant integration follows a specific quality scale rule, checking whether it implements the required patterns, configurations, or code structures defined by the quality scale system. Use when asked to check a rule (e.g. "check if the peblar integration follows the config-flow rule") or to verify an integration reaches a quality tier (Bronze, Silver, Gold, Platinum).
- bump-dependencyBumps a Python package dependency across Home Assistant Core integrations, regenerates core requirement files, runs verification tests and prek lint, and prepares a pull request with proper release/compare links.
- react-component-performanceAnalyze and optimize React component performance issues (slow renders, re-render thrash, laggy lists, expensive computations). Use when asked to profile or improve a React component, reduce re-renders, or speed up UI updates in React apps.
- trace-regressionTrace a reported dotnet/maui issue to the commit or PR that introduced its regression using release boundaries, source history, and linked evidence. Use for "/issue trace-regression", "which PR introduced this issue", or "trace this regression". Distinguish confirmed introductions from likely candidates and missing evidence. Report-only; not PR regression-risk review, CI failure triage, or automatic bug fixing.
- parallel-feature-developmentCoordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system simultaneously, when establishing file ownership to prevent merge conflicts in a shared codebase, when designing interface contracts so parallel implementers can build against each other's APIs before they are ready, or when deciding whether to use vertical slices versus horizontal layers for a full-stack feature.