Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Operate Holded ERP through holdedcli to read and update data safely. Use when the user asks to read, search, create, update, or delete Holded entities (conta...
Operate Holded ERP through holdedcli to read and update data safely. Use when the user asks to read, search, create, update, or delete Holded entities (conta...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Use holdedcli to read and modify Holded data with a safe, repeatable workflow.
Confirm technical prerequisites. Discover available actions with holded actions list. Inspect the selected action with holded actions describe <action> --json. Classify the action as read or write. If it is a write operation, ask for explicit confirmation before execution. Run with --json and summarize IDs, HTTP status, and applied changes.
Verify that the binary exists: holded help Verify credentials: holded auth status or HOLDED_API_KEY Prefer structured output whenever possible: --json
ALWAYS check deductibility rules BEFORE creating any document. See "Accounting Rules for Spain" section below. Treat any POST, PUT, PATCH, or DELETE action as write. Treat any GET action (or HEAD when present) as read. Before any operation, always run holded actions describe <action> --json (after holded actions list) to validate accepted parameters. For purchase receipts, always enforce docType=purchase and include "isReceipt": true in the JSON body. Since holdedcli validates against Holded's schema (which doesn't include isReceipt), you must use --skip-validation flag. Ask for explicit user confirmation every time before any write action. Do not execute writes on ambiguous replies (ok, go ahead, continue) without clarification. Repeat the exact command before confirmation to avoid unintended changes. If the user does not confirm, stop and offer payload adjustments.
Before any write action, show: Holded action (action_id or operation_id). Method and endpoint. --path, --query, and body parameters (--body or --body-file). The exact command to run. Use this format: This operation will modify data in Holded. Action: <action_id> (<METHOD> <endpoint>) Changes: <short summary> Command: holded actions run ... --json Do you confirm that I should run exactly this command? (reply with "yes" or "confirm") Execute only after an explicit affirmative response.
Locate the action with holded actions list --json (use --filter). Verify accepted path/query/body parameters with holded actions describe <action> --json. Run holded actions run <action> ... --json. Return a clear summary and relevant IDs for follow-up steps.
Locate and validate the action. Run holded actions describe <action> --json to verify required/optional parameters. Prepare the final payload. If creating a purchase receipt/ticket, verify docType=purchase and "isReceipt": true, and use --skip-validation flag. Request mandatory confirmation. Run the command after confirmation. Report result (status_code, affected ID, API response).
holded auth set --api-key "$HOLDED_API_KEY" holded auth status holded ping --json holded actions list --json holded actions list --filter contacts --json holded actions describe invoice.get-contact --json holded actions run invoice.get-contact --path contactId=<id> --json For long payloads, prefer --body-file: holded actions run invoice.update-contact \ --path contactId=<id> \ --body-file payload.json \ --json Purchase receipt rule (mandatory for purchase tickets): holded actions describe invoice.create-document --json holded actions run invoice.create-document \ --path docType=purchase \ --body '{"isReceipt": true, "date": 1770764400, "contactId": "<contactId>", "items": [{"name": "Description", "units": 1, "subtotal": 29.4, "tax": 0}]}' \ --skip-validation \ --json Important notes: Use --skip-validation flag because holdedcli validates against Holded's schema which doesn't include isReceipt. Use subtotal in items (not price) - this is the field name Holded's API expects. Timestamps must be in seconds (Unix epoch) and in Europe/Madrid timezone. Timestamp calculation (Python): from datetime import datetime, timezone, timedelta # For 11/02/2026 00:00 in Madrid: dt = datetime(2026, 2, 11, 0, 0, 0, tzinfo=timezone(timedelta(hours=1))) print(int(dt.timestamp())) # 1770764400
⚠️ ALWAYS check these rules BEFORE creating any expense document: Expense TypeIVA DeductibleExpense DeductibleAccountRestaurants/Meals❌ No✅ Yes (with justification)629Displacement❌ No✅ Yes629Fuel⚠️ Mixed✅ Yes625/622Office supplies✅ Yes✅ Yes600/602Insurance⚠️ Mixed✅ Yes625 Before creating any document, ALWAYS verify: Is the expense tax deductible? Is the IVA deductible? (usually NO for restaurants, displacement) If in doubt, ASK before creating the document. Common mistake to avoid: Never set tax: 10 or tax: 21 for restaurant expenses - IVA is NOT deductible for meals unless it's a business event with proper justification.
If MISSING_API_KEY appears, configure API key through --api-key, HOLDED_API_KEY, or holded auth set. If ACTION_NOT_FOUND appears, list the catalog and search with --filter. If INVALID_BODY appears, validate JSON before execution. If API_ERROR appears, report status_code and the API snippet.
Read {baseDir}/references/holdedcli-reference.md for quick commands and criteria. Use dynamic action discovery and parameter inspection via: holded actions list --json holded actions describe <action> --json
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.