Access Inventory for Openclaw

A strategic protocol and inventory system that prevents AI agents from falsely claiming they lack access to tools, APIs, or services.

joeytbuilds
v1.0.0
Apr 15, 2026
0
728
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install access-inventory

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install access-inventory using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Access Inventory?

Access Inventory is a specialized methodology designed for Openclaw Skills users to solve the 'uncertainty problem' in AI agents. By default, many agents hedge and refuse to perform tasks, claiming they lack necessary API keys or permissions even when those credentials exist locally.

This skill provides a structured framework within your documentation to override this cautious behavior. It combines a hard directive rule with a comprehensive inventory table, ensuring the agent knows exactly what tools are authenticated and where secrets are stored, shifting the agent's behavior from passive hesitation to active execution.

Access Inventory Use Cases

  • Preventing agents from saying "I don't have an API key" for services you have already configured.
  • Streamlining multi-tool workflows where the agent needs to jump between GitHub, Stripe, and local CLIs.
  • Reducing user friction by ensuring agents try commands before reporting permission errors.
  • Onboarding new AI agents to a complex local development environment with many hidden config files.

How Access Inventory Works

  1. The user implements a Hard Override Rule in the agent instructions that forbids the agent from claiming a lack of access.
  2. A detailed Inventory Table is created listing every authenticated CLI and the specific file paths for API keys.
  3. The agent checks this inventory as its primary source of truth before starting a task.
  4. If a tool is not explicitly listed, the agent follows a fallback discovery protocol (checking env vars and config directories) before asking the user for help.
  5. The agent proceeds with the 'try-first' mentality, reporting actual technical errors only after an execution attempt fails.

Access Inventory Setup

To implement this within your Openclaw Skills workflow, follow these steps:

  1. Inject the Override Rule: Add a section to your AGENTS.md titled ACCESS — NEVER CLAIM YOU LACK IT that mandates the agent must always try to run commands first.
  2. Audit Your System: Run the following commands to identify what the agent has access to:
# Find existing API keys
ls ~/.config/

# List installed CLI tools
brew list || which <toolname>

# Check for active environment variables
env | grep -i "key\|token\|secret"
  1. Map the Inventory: Create the markdown tables for 'Authenticated CLIs' and 'API Keys' as defined in the skill documentation.

Access Inventory Data Schema & Taxonomy

The Access Inventory skill organizes data through a structured hierarchy in your agent's context:

Component Type Purpose
Override Rule Markdown Header Sets the behavioral policy for the agent.
Authenticated CLIs Markdown Table Lists Tool, Status (✅/❌), and Authentication Notes.
API Keys Markdown Table Lists Service Name and specific file path Location.
Discovery Protocol Ordered List Defines the 5-step fallback logic for unlisted services.
Maintenance Cycle Task List Defines the weekly heartbeat for rotating keys and updating tools.

Access Inventory Advanced Features

  • Multi-Agent Support: Share the same inventory across different specialized agents to maintain a consistent source of truth.
  • Automated Discovery Hooks: Potential to script the inventory update to run as a pre-commit or post-install hook.
  • Environment-Specific Tables: Create different inventory sections for production, staging, and local development environments.
  • Fallback Hierarchy: A structured 5-point search plan that forces the agent to exhaust all local possibilities before interrupting the human user.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*