DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to package an agent so teammates can install it with Raw CLI

Export a configured agent with its tools and skills as a .rawpkg for your team.

Authorization notice. Raw CLI is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Credentials. Do not pack a literal api_key value into the package; the recipient should set their own credentials through api_key_env or their own config.

Who it is forA team lead who built a project helper agent and needs coworkers on other machines to run the same tools and skills with their own model.

The problemSetting up the same agent on each teammate's machine by hand means repeated copying of tools, skills and settings.

The outcomeA .rawpkg archive that a teammate installs and binds to their own model alias, keeping the same agent behavior.

What you need first

  • Node.js 22.13+ on macOS, Linux or Windows 10/11
  • Bash for the bash tool (Git Bash on Windows, or PowerShell if Bash is absent)
  • A local model served over an OpenAI-compatible endpoint, or a hosted model with an API key
  • Comfort editing a strict JSON config file

Steps

  1. Run raw package export --agent NAME --name @owner/name --version 1.0.0 --out DIR.
  2. Run raw package pack DIR --out FILE.rawpkg.
  3. Send FILE.rawpkg to the teammate and have them run raw package install FILE.rawpkg --as kit.
  4. Have the teammate run raw agent add NAME --from pkg/kit/agents/EXPORT --model MODEL_ALIAS with their own model alias.
  5. Run raw --agent NAME "task" on the recipient machine to confirm it works. (inferred, check the README)

Prompt for your agent

Export the configured agent <agent-name> from the repo lploc94/raw-cli as a package named @<owner>/<name> version 1.0.0, pack it into <file>.rawpkg, and list the steps the recipient needs to bind their own model. Expected output: a packed .rawpkg file and a short recipient checklist. Verify the package file exists and contains no literal API keys.

Caveat. Updates keep the recipient's local model binding, but the README does not describe how credentials are handled beyond the api_key_env and api_key fields.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page