How do I install the Zoats skill?

Run npx skillmds@latest add thevibethinker/zoats in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Zoats safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Zoats?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Zoats free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

thevibethinker (@thevibethinker) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Zoats by thevibethinker — Agent Skill

Name: Zoats
Author: thevibethinker

Zoats

Safe, archived Skill wrapper for the former standalone ZoATS applicant-tracking-system repo. Use when inspecting, packaging, validating, or exporting ZoATS as a reusable Zo skill scaffold; do not install live routes or run candidate/employer workflows on V's Zo without explicit approval.

thevibethinker 41ce2c3 146 files · 561.7 KB Updated Sep 17, 2026

File contents

ZoATS Skill

ZoATS is preserved here as a reusable Skill package migrated from the former dedicated private repo thevibethinker/ZoATS.

Current Status

The dedicated GitHub repo is not deleted.
This Skill is a local, sanitized migration target for verification.
ZoATS should not be run as a live ATS on V's Zo by default.
Live zo.space routes from the old scaffold were removed separately before this migration.

Safety Rules

Do not provision /careers, /api/zoats/*, or other public routes unless V explicitly asks.
Do not send emails, process real candidates, or write external state unless V explicitly authorizes that action.
Treat jobs/ contents as fixtures/examples only. Real hiring data does not belong in the skill source tree.
Keep runtime settings out of source. Use config/settings.example.json as the template; local runtime config should be generated outside committed source.
Before exporting publicly, run a redaction scan and remove any private employer/candidate examples.

Useful Commands

# Inspect package shape
python3 Skills/zoats/scripts/verify_skill_package.py

# Run unit tests without live external effects
pytest Skills/zoats/tests

# Inspect original repo migration metadata
cat Skills/zoats/references/migration/source-manifest.json

Important Paths

references/original-repo-readme.md — original repo README preserved as reference.
references/migration/source-manifest.json — source repo, commit, exclusions, deletion status.
scripts/ — installation/provisioning helpers. Use cautiously; some helpers can create zo.space routes.
space-routes/ — template route sources, retained for packaging/export only.
tests/ — package/test harness.

Deletion Gate

Only delete or archive the dedicated GitHub repo after verifying:

Skills/zoats/SKILL.md exists and parses as a valid skill.
The copied tree includes the expected source, docs, schemas, workers, tests, and route templates.
Private/runtime files were excluded.
Tests or import checks pass to the level expected for a preserved package.
V explicitly approves the repo deletion/archive step.

---name: zoatsdescription: Safe, archived Skill wrapper for the former standalone ZoATS applicant-tracking-system repo. Use when inspecting, packaging, validating, or exporting ZoATS as a reusable Zo skill scaffold; do not install live routes or run candidate/employer workflows on V's Zo without explicit approval.---# ZoATS SkillZoATS is preserved here as a reusable Skill package migrated from the former dedicated private repo `thevibethinker/ZoATS`.## Current Status- The dedicated GitHub repo is **not deleted**.- This Skill is a local, sanitized migration target for verification.- ZoATS should **not** be run as a live ATS on V's Zo by default.- Live zo.space routes from the old scaffold were removed separately before this migration.## Safety Rules1. Do not provision `/careers`, `/api/zoats/*`, or other public routes unless V explicitly asks.2. Do not send emails, process real candidates, or write external state unless V explicitly authorizes that action.3. Treat `jobs/` contents as fixtures/examples only. Real hiring data does not belong in the skill source tree.4. Keep runtime settings out of source. Use `config/settings.example.json` as the template; local runtime config should be generated outside committed source.5. Before exporting publicly, run a redaction scan and remove any private employer/candidate examples.## Useful Commands```bash# Inspect package shapepython3 Skills/zoats/scripts/verify_skill_package.py# Run unit tests without live external effectspytest Skills/zoats/tests# Inspect original repo migration metadatacat Skills/zoats/references/migration/source-manifest.json```## Important Paths- `references/original-repo-readme.md` — original repo README preserved as reference.- `references/migration/source-manifest.json` — source repo, commit, exclusions, deletion status.- `scripts/` — installation/provisioning helpers. Use cautiously; some helpers can create zo.space routes.- `space-routes/` — template route sources, retained for packaging/export only.- `tests/` — package/test harness.## Deletion GateOnly delete or archive the dedicated GitHub repo after verifying:- `Skills/zoats/SKILL.md` exists and parses as a valid skill.- The copied tree includes the expected source, docs, schemas, workers, tests, and route templates.- Private/runtime files were excluded.- Tests or import checks pass to the level expected for a preserved package.- V explicitly approves the repo deletion/archive step.

Frequently asked questions