Metadata-Version: 2.4
Name: agentforge-cli
Version: 0.1.0
Summary: Registry and trust layer for AI agent skills
Requires-Python: >=3.10
Description-Content-Type: text/markdown
Requires-Dist: typer>=0.9.0
Requires-Dist: rich>=13.0.0
Requires-Dist: httpx>=0.25.0
Requires-Dist: pyyaml>=6.0

# agentforge (CLI: forge)

Registry and trust layer for AI agent skills. This package provides the **forge** command so you can create, inspect, publish, and install skills from the terminal.

## Install

```bash
pip install agentforge-cli
```

## Use

From any directory:

```bash
forge init              # scaffold a skill (skill.yaml + example code)
forge inspect           # show permissions and risk for the skill here
forge publish           # publish to the registry
forge search            # list skills
forge install <slug>    # record an install
```

**Registry URL (what `-r` is for)**  
The **registry** is the backend API that stores and serves skills. When you deploy the AgentForge backend (e.g. on Render or Railway), you get a URL like `https://agentforge-api.onrender.com`. That URL is your **registry URL**.

- **`forge publish`** sends your skill to that API so it appears on the website and in `forge search`.
- **`forge search`** and **`forge install`** read from that same API.

If you don’t pass `-r`, the CLI defaults to `http://localhost:8000` (your own API running on your machine). For the **public** registry, pass its URL:

```bash
# Example: your backend is at https://agentforge-api.onrender.com
forge publish -r https://agentforge-api.onrender.com
forge search -r https://agentforge-api.onrender.com
forge install send-email -r https://agentforge-api.onrender.com
```

So `https://your-api.example.com` in the docs is a **placeholder** for whatever your real backend URL is (e.g. from Render or Railway).

## Links

- [AgentForge](https://github.com/vince13/AgentForge) — repo and docs
