Installed binary is `meta` but README and bundled skill call `meta-cli` (skill fails without a manual symlink)

[hoangvantuan]

Summary

go install github.com/ygncode/meta-cli/cmd/meta@latest installs a binary named meta, but the README and the bundled Claude Code skill (skill/meta-cli-fb) invoke the tool as meta-cli. As a result, the skill fails out of the box unless the user manually creates a symlink/alias.

Environment

• OS: macOS (darwin/arm64)
• Go: 1.26.4
• Install command: go install github.com/ygncode/meta-cli/cmd/meta@latest

Steps to reproduce

go install github.com/ygncode/meta-cli/cmd/meta@latest
ls "$(go env GOPATH)/bin"      # -> meta   (NOT meta-cli)

meta pages list --json         # works fine
meta-cli pages list --json     # command not found

Actual behavior

• The installed binary is meta (Go names the binary after the cmd/meta directory).
• meta works correctly — auth, pages list --json, etc. all return valid data.
• meta-cli is not found in PATH.

Expected behavior

The command name should be consistent across the binary, the README, and the skill.

Impact on the bundled skill

skill/meta-cli-fb/SKILL.md is entirely written against meta-cli, and its frontmatter declares:

metadata: {"openclaw": {"requires": {"bins": ["meta-cli"]}}}

Every command in the skill (meta-cli post ..., meta-cli comment hide ..., meta-cli messenger send ...) will fail because the binary is actually meta. Users have to manually run something like:

ln -s "$(go env GOPATH)/bin/meta" "$(go env GOPATH)/bin/meta-cli"

before the skill works, which is easy to miss.

Suggested fixes (pick one)

1. Rename the command directory cmd/meta -> cmd/meta-cli so go install .../cmd/meta-cli@latest produces a meta-cli binary that matches the docs and skill. (Most consistent.)
2. Standardize on meta: update the README and skill/meta-cli-fb/SKILL.md (including requires.bins) to use meta instead of meta-cli.
3. At minimum, add an explicit note in the README/install section instructing users to symlink/alias meta -> meta-cli so the skill resolves correctly.

Happy to send a PR for option 1 or 2 if you have a preference. Thanks for the tool — the Facebook Page skill is otherwise excellent.