Let Your AI Agent Manage aweskill for You — aweskill<br>Most developer tools still assume the human is the operator.

You read the documentation. You install the CLI. You decide where files should go. You copy commands from a README, paste them into a terminal, check the output, fix the path, and then explain the final state back to your AI coding agent.

That made sense when tools were only built for humans.

But AI coding agents now run commands, inspect files, follow project conventions, and repair broken local state. If a tool is meant to help agents, the better question is not:

How does a human use this CLI?

It is:

Can the agent operate the CLI by itself?

That is one of the quiet but important ideas behind aweskill: it is a CLI-first Skill package manager that AI agents can operate themselves.

Website: aweskill.webioinfo.top

The Old Workflow: You Manage the Agent’s Tools

When a new AI Agent needs a Skill, the usual workflow looks like this:

You find the Skill.

You download or copy it.

You locate the agent’s Skill directory.

You place SKILL.md in the right folder.

You restart the agent.

You hope the next agent uses the same layout.

This is manageable once.

It becomes messy when you use Codex, Claude Code, Cursor, Gemini CLI, Windsurf, Qwen Code, OpenCode, or any other coding agent side by side. Each one has its own directory layout and conventions. The human becomes the package manager.

That is backward.

If the agent is already capable of editing your repo, running tests, and diagnosing failures, it should also be able to manage its own Skills.

The aweskill Workflow: Give the Agent a Protocol

aweskill provides a bootstrap document written for AI coding agents:

Read https://github.com/mugpeng/aweskill/blob/main/README.ai.md and follow it to install aweskill for this agent.<br>That instruction is enough for a capable coding agent to do the initial setup.

The protocol tells the agent to:

check that Node.js and npm are available

install aweskill globally

initialize the central Skill store at ~/.aweskill/skills/

detect the current agent runtime

project the built-in aweskill and aweskill-doctor Skills into that agent

verify the projection

ask you to restart so the new Skills become active

After that restart, you no longer have to remember every command. You can ask the agent in plain language.

What the Agent Can Do After Bootstrap

aweskill ships two built-in meta-Skills:

aweskill: routine Skill management, including search, install, update, bundles, and agent projection

aweskill-doctor: repair-first workflows, including sync checks, cleanup, deduplication, malformed SKILL.md repair, and recovery

Once these are projected into the current agent, the agent can translate natural-language requests into aweskill commands.

Instead of typing:

aweskill find review<br>aweskill install owner/repo<br>aweskill agent add skill pr-review --global --agent codex<br>You can say:

Find a good code-review Skill, install it into aweskill, and enable it for this agent.<br>The agent can search, inspect results, choose an installable source, run the install, project the Skill, and verify the result.

That is the difference between a CLI that agents can call and a CLI that humans must babysit.

Use Case 1: Bootstrap a Fresh Agent

You open a new machine, a fresh terminal, or a newly installed coding agent. Instead of manually setting up its Skill directory, you give it one instruction:

Read README.ai.md from the aweskill repo and install aweskill for this agent.<br>The agent follows the bootstrap protocol:

npm install -g aweskill<br>aweskill store init<br>aweskill store where --verbose<br>aweskill agent supported<br>aweskill agent add skill aweskill,aweskill-doctor --global --agent agent-id><br>aweskill agent list --global --agent agent-id><br>The important detail is that the protocol is conservative. If the agent cannot determine the correct agent-id, it should ask you instead of guessing. It should not project Skills to every installed agent by default.

That makes the bootstrap flow agent-friendly without being reckless.

Use Case 2: Ask the Agent to Find and Install a Skill

You are working on a Python data project and want a useful data-analysis Skill.

You do not need to browse registries yourself. You can ask:

Find a useful Python data-analysis Skill and install the best match into aweskill.<br>The agent can run:

aweskill find python data analysis<br>Then it can inspect the results, avoid unsupported discover-only entries, install the best available source, and report what it did:

aweskill install source><br>If the Skill should be active in the current agent, the agent can project it:

aweskill agent add skill skill-name> --global --agent agent-id><br>The human stays in the loop for judgment. The agent handles the mechanical work.

Use Case 3: Build a Project Bundle by Conversation

Bundles are where agent-operated Skill management starts to feel natural.

Instead of remembering which Skills belong in a frontend project, you can...