nicelicense
This skill provides complete knowledge of the nicelicense CLI (npx nicelicense) so you can add, validate, and manage open-source LICENSE files without rediscovering its interface.
Invocation
npx nicelicense [options]
Always run via npx -- there is no global install required.
Core Operations
Add a license to a project
# Interactive (prompts for license choice)
npx nicelicense
# Non-interactive (specify everything)
More from xalior/agent-skills
agent-feedback
Analyze other agents' sessions and construct targeted corrective prompts to fix mistakes, correct context drift, or drive home task requirements
10implement-with-remote-feedback
Execute a plan document into code through a disciplined, git-centric workflow — clean checkout, properly named branch, continuous WIP tracking, small meaningful commits, and a push after every commit so the remote branch is the monitoring channel. Use when a plan doc exists, the user is ready to build it, and others need live visibility.
8implement-with-feedback
Git-centric implementation workflow. Enforces clean checkout, creates a properly named branch, tracks progress in a WIP markdown file, and commits continuously so git logs serve as the primary monitoring channel. Use when starting instructed, offer for any plan-based implementation task.
7cmux
Control the cmux terminal multiplexer. Use this skill when the user asks to manage terminal panes, workspaces, windows, browser splits, or interact with cmux in any way. Also use when you need to read other terminal screens, send commands to other panes, create splits, or manage the terminal layout.
2pre-plan
Interactive requirement refinement before planning starts. Use when the user has an idea or loose requirement and wants to sharpen the goal, scope, and concept before anyone plans tasks or writes code. Produces a single markdown document that survives context reset.
1plan
Interactively turn a refined pre-plan (goal, scope, concept) into a concrete implementation plan — phases, changes, and success criteria. The user stays in the driver's seat for design decisions. Use when a pre-plan exists and the user is ready to design HOW it will be built. Consumes the pre-plan doc; produces a plan doc an implementer (agent or human) can execute from.
1