openclaw-onur-inventory

Refresh, audit, and annotate the OpenClaw Onur inventory from Gitcrawl data.

12|2|Updated Jan 2, 2026
One-click install
npx skills add https://github.com/osolmaz/tools --skill openclaw-onur-inventory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-onur-inventory
Source: https://github.com/osolmaz/tools/tree/main/agents/skills/openclaw-onur-inventory
Command: npx skills add https://github.com/osolmaz/tools --skill openclaw-onur-inventory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the upkeep and governance of the OpenClaw Onur inventory by periodically refreshing, auditing, and annotating inventory items.

Core Features & Use Cases

  • Periodic curation of OPENCLAW_ONUR_INVENTORY.md using Gitcrawl data.
  • Generation of candidate review pools and a machine-readable inventory export for notifier comparison.
  • End-to-end automation with sandboxed execution, an auditable finalization workflow, and a clear regeneration path for inventory state.

Quick Start

Run the inventory maintenance workflow in the sandbox to refresh /workspace/OPENCLAW_ONUR_INVENTORY.md from /gitcrawl/gitcrawl.db and export the inventory JSON.

Frequently Asked Questions about openclaw-onur-inventory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub inventory maintenance from a crawled database?

Automating GitHub inventory maintenance periodically refreshes and audits items from a Gitcrawl database to curate an inventory file and export a machine-readable JSON. This skill runs scheduled cron-like workflows to process Gitcrawl data and generate an auditable inventory state.

What is the best way to curate a markdown inventory from Gitcrawl data on a schedule?

Curating a markdown inventory from Gitcrawl data on a schedule uses periodic cron-like runs to refresh the inventory file and write candidate review pools to a state directory. It enforces sandboxed execution and scripted finalization workflows to ensure safe, auditable updates.

Does this inventory automation approach support read-only Git crawl exports?

Yes, this inventory automation approach supports read-only Git crawl exports by enforcing sandboxed execution during periodic refresh cycles. It securely processes crawled data to annotate inventory items and export a JSON file for notifier comparisons without modifying the source database.

How does the inventory finalization workflow generate a machine-readable JSON export?

The inventory finalization workflow generates a machine-readable JSON export by annotating curated items and writing candidates to a state directory. This JSON output is structured for notifier comparisons, allowing the refreshed inventory state to be automatically compared against external notifications.

Why does the automated inventory refresh require sandboxed execution?

Automated inventory refresh requires sandboxed execution to enforce safe, auditable updates when processing Gitcrawl data and writing to the state directory. This isolation prevents unintended side effects during the scripted finalization workflow and protects the generated inventory JSON integrity.