| name | openclaw-onur-inventory |
| description | Use when maintaining the OpenClaw Onur inventory repository, including periodic roughly every-2-hour refreshes, auditing OpenClaw local model and open-weight model issue/PR inventories, deciding whether a thread belongs in that file, sorting the inventory, updating the reviewed-through issue/PR watermark, or explaining why an item was included or excluded. |
OpenClaw Onur Inventory
Use this skill for OPENCLAW_ONUR_INVENTORY.md in the OpenClaw Onur inventory repository.
The inventory is curated. Do not regenerate it by dumping keyword hits.
Periodic Cadence
Run this inventory maintenance periodically, normally about every 2 hours when the user asks for ongoing upkeep.
Each run must refresh live state, scrutinize candidates, update/curate the onurclaw inventory file if anything changed, sort it, and commit/push the onurclaw repo changes.
For unattended automation, use the public hardened job contract in docs/inventory-job.md. The cron prompt must tell the sandboxed agent to read /workspace/.agents/skills/openclaw-onur-inventory/SKILL.md, curate /workspace/OPENCLAW_ONUR_INVENTORY.md from /gitcrawl/gitcrawl.db, write candidates with scripts/list_inventory_review_candidates.py --format jsonl --output /state/inventory-candidates.jsonl, review that file in small chunks, then run /workspace/scripts/finalize_inventory_job.sh. The finalizer must export /workspace/OPENCLAW_ONUR_INVENTORY.json and notifier comparison must read that JSON, not parse Markdown tables. Do not reduce the cron job to a wrapper-only sort/compare step. Do not document or expose host-specific paths, credentials, message destinations, or the private security topology in public files. The automated runner must use an isolated sandbox, read-only exported Gitcrawl/notifier data, no network egress, no host secrets, and host-side pushing only. The sandbox does not have Codex apply_patch; use checked-in scripts or simple preflightable shell/Python commands for mechanical edits.