From license-populator
Take a template from the user's license template store and populate its placeholders ({{year}}, {{copyright_holder}}, {{project_name}}, etc.), then write the result as LICENSE (or a user-specified path) in the current project. Use when the user says "add MIT license", "populate the apache template here", or after recommend-license points to an existing template.
How this skill is triggered — by the user, by Claude, or both
Slash command
/license-populator:populate-from-templateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Render a stored template into a concrete LICENSE file.
Render a stored template into a concrete LICENSE file.
template_store_path. If config missing, invoke setup-template-store.name (case-insensitive).list-templates first and ask the user to pick.{{token}} placeholders.{{year}} → current year (or range if user specifies).{{copyright_holder}} → ask the user; default to git user.name from git config user.name if available.{{project_name}} → infer from current directory basename; confirm with user.LICENSE in the current working directory.LICENSE already exists, show a diff and ask before overwriting.LICENSE.md, docs/LICENSE).git add LICENSE (do not commit unless asked).package.json, pyproject.toml, Cargo.toml, etc. only if the user explicitly asks — do not silently mutate manifests.{{token}} and warn — do not invent values.npx claudepluginhub danielrosehill/claude-code-plugins --plugin license-populatorCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.