AWORG

How-Tos

Publish a package

Zip it, upload it, and it's live. Versions, names and what the store checks.

Publishing

  1. Make an account.
  2. Zip your package's folder. Zipping the folder or just its contents both work.
  3. Go to Publish, choose the zip, and submit.

The store works out the type from the files, checks the package, and publishes it immediately at aworg.com/skills/<name>, /tools/<name> or /personas/<name>.

Names

  • The name comes from name: in SKILL.md or PERSONA.md, or from the folder name for a tool.
  • 2 to 40 characters: lowercase letters, numbers, - and _, starting with a letter.
  • First come, first served, per type. skills/weather and tools/weather are different packages and can belong to different people. Once you've published a name, only you can publish new versions of it.
  • A few names are reserved: AWORG's built-in capabilities, and the personas AWORG ships with.

Versions

  • Three numbers: 1.0.0.
  • Taken from the upload form, then from version: in the frontmatter (or VERSION in a tool's __init__.py), and otherwise the next number up from your last version.
  • A published version can't be replaced. Fix a mistake by publishing a new version. Versions must count up.
  • You can withdraw a version, and it stops being offered as the latest. You can remove a whole package, and it disappears from the store. Both can be undone from the package page.

What the store checks

  • It's a zip, under 25 MB, unpacking to under 100 MB and 500 files.
  • No absolute paths, no .., no symbolic links.
  • A skill or persona has a name and a description.
  • A tool has at least one tool file with NAME and DESCRIPTION as plain strings, no syntax errors, and doesn't claim INTERNAL or REQUIRED.
  • __pycache__, .pyc, .git, .DS_Store and __MACOSX are dropped quietly.

The store never runs what you upload. It rebuilds the zip with your files under <name>/ and publishes its SHA-256, so what an Aworg downloads is exactly what the package page shows.