Why use it: this route doesn't touch the terminal and doesn't create any files in the project repo. In exchange, it only runs on Claude Code.
What it generates: a marketplace named humanizer and a plugin humanizer in your Claude Code configuration. The skill invocation command becomes /humanizer:humanizer.
All commands below are typed in the Claude Code chat box, not in the terminal. Typing them into the shell will report
command not found.
Requirements
Claude Code 2.1.142 or later. Check with the terminal:
claude --version
Steps
In the Claude Code chat:
/plugin marketplace add blader/humanizer
/plugin install humanizer@humanizer
The syntax humanizer@humanizer is <tên plugin>@<tên marketplace>. The two names are identical because .claude-plugin/marketplace.json sets name: "humanizer" and declares exactly one plugin also named humanizer, source: "./".
Verify the installation is correct
/plugin
The plugin table must show humanizer version 2.11.2 (value taken from .claude-plugin/plugin.json → version).
To verify the manifest before installing, run in the terminal on a clone:
claude plugin validate .
Real output when healthy:
Validating marketplace manifest: <đường-dẫn>/.claude-plugin/marketplace.json
✔ Validation passed
Invoke the skill
/humanizer:humanizer
[dán văn bản vào đây]
Installing via the Skills CLI (workflow 01) gives a shorter name: /humanizer. Invoking with a natural sentence ("humanize this paragraph for me") works on both installation routes, because Claude matches on the field description in the metadata of SKILL.md.
Choose 01 or 02
Choose only one. Installing both means two identical prompt copies are loaded together, and the agent may easily pick the old one when you update one side. If you accidentally install both, remove the Skills CLI one with npx skills remove humanizer --agent claude-code -y.