catalog

What This Skill Does

The catalog skill provides a streamlined, real-time interface for users to query service offerings, pricing, and duration directly from the studio's local records. Designed as a foundational "hello world" implementation, this skill bridges the gap between static user requests and dynamic local data. When invoked, it triggers a backend script that parses a local JSON file, ensuring that the information provided to the user is always accurate, current, and consistent with the studio's master records. Instead of hardcoding prices in the AI model, the catalog skill maintains a clean separation between the knowledge base and the interface logic, making it easy for studio owners to update their offerings simply by modifying the underlying data file without needing to retrain or reconfigure the agent.

Installation

To integrate this skill into your environment, use the ClawHub CLI. Ensure your OpenClaw agent has the necessary permissions to execute local Node.js scripts. Run the following command in your terminal:

clawhub install openclaw/skills/skills/rodbalbino/catalog

Once installed, the skill will register itself with the agent's task executor, allowing the AI to call node {baseDir}/catalog.js whenever it identifies a relevant user query.

Use Cases

This skill is ideal for service-based businesses, such as creative studios, consulting firms, or freelance collectives, that need to provide immediate, reliable answers regarding their service menu. It replaces the need for users to navigate away from the chat interface to a website, providing instant clarity on costs and time commitments.

Example Prompts

1. "What services do you offer and what are their prices?"
2. "How much would it cost to hire you for a project and how long does it usually take?"
3. "List all available services and their associated durations."

Tips & Limitations

This skill is a lightweight integration. It is strictly limited to the data provided by the local JSON output. It does not perform e-commerce processing, payment collection, or scheduling. If you need to extend the catalog to include images or complex hierarchies, ensure your JSON schema remains compatible with the core parser. Always keep the {baseDir}/catalog.js file path updated if you migrate your agent's directory structure to avoid runtime execution errors. The agent will respond best when prompted with clear, direct intent.