Where to put Skill folders

Recommended targets

HowAI's cursor option chooses the shared personal directory. For another supported directory, use an absolute --target. These examples describe the intended targets; managed, legacy and remote environments can have additional rules in the agent's official documentation.

Keep the package one level below the parent

~/.agents/skills/
  cobalt-system-deck/
    SKILL.md
    ...supporting files...

~/.agents/skills/
  cobalt-system-deck/
    cobalt-system-deck/
      SKILL.md

An archive can contain a wrapper folder. Move the complete inner Skill folder into the target instead of leaving two copies of the name nested together. Do not copy only SKILL.md if it refers to sibling resources.

Choose personal or project scope

A personal directory is useful for methods you use across projects. A repository directory keeps a reviewed package near a team's inputs and conventions. Do not distribute a package through a repository without checking its terms.

npx --yes https://howai.build/cli/howai-cli-0.1.5.tgz install cobalt-system-deck --api https://howai.build --target "$PWD/.agents/skills"

HowAI requires the absolute parent directory. Use the physical path when a shell or temporary directory resolves through a symbolic link. On Windows, supply the complete drive path rather than copying a Unix path.

Find duplicate or unexpected copies

• Read the path printed by HowAI install or list.
• Inspect both personal and repository locations.
• Check the name and version inside the folder the agent reports using.
• Remove or move only the reviewed redundant copy.
• Refresh the agent session after changing files.

Do not assume that different agents share one precedence rule. The installed package and the active package can differ when multiple scopes contain the same name.

Remote environments need reachable files

A cloud session or remote machine has a different filesystem. Provide a supported project copy or follow the agent's official sync mechanism. Recheck runtimes and tool authorization there; local setup alone does not establish remote readiness.

FAQ