agentsclimarketplace
Sign in

Zoats

Skill thevibethinker/vibe-thinker-skills/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.From its SKILL.md

Install
npx -y skills add thevibethinker/vibe-thinker-skills --skill zoats

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.7 KB, 474 tokens by cl100k_base, as published. Nobody here has run it

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

  1. 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

# 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.

What ships with it: 145 files

559.2 KB alongside SKILL.md, 73 of them executable

commands/

config/

docs/

inbox_drop/

jobs/

lib/

pipeline/

references/

scheduled_tasks/

105 more files not listed here. See all 145 in the repository.

Gives 0 of the 12 instructions most hr recruiting skills give in 474 tokens

Counted across 356 of the 357 authors here whose files we hold, read 2026-08-07

  • Quantify achievements with specific metricsin 14 of 356, across 6 files
  • Keep the resume under two pagesin 14 of 356, across 6 files
  • Request the full job description if not providedin 12 of 356, across 4 files
  • Extract keywords and prioritize job requirementsin 12 of 356, across 4 files
  • Stop and ask for clarification if required inputs are missingin 12 of 356, across 5 files
  • Map candidate experience to job requirementsin 11 of 356, across 3 files
  • Ask if the user wants adjustmentsin 11 of 356, across 3 files
  • Provide strengths and gap analysis after the resumein 10 of 356, across 2 files
  • Request candidate background details if not providedin 10 of 356, across 2 files
  • Format experience bullets as action verb plus resultin 10 of 356, across 2 files
  • Ask for missing inputs before startingin 10 of 356, across 9 files
  • Use exact job description terminologyin 9 of 356, across 1 file

Said here and by no other author read

  • run verify_skill_package.py to inspect package shape
  • run pytest on tests without live external effects
  • treat jobs contents as fixtures examples only
  • keep runtime settings out of source
  • run a redaction scan before exporting publicly
  • verify SKILL.md exists and parses before deletion

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.