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.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin license-populatorThis skill uses the workspace's default tool permissions.
Render a stored template into a concrete LICENSE file.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
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.