fabric-api

What This Skill Does

The fabric-api skill provides a robust interface for interacting with the Fabric workspace via its HTTP API. This skill acts as a bridge between OpenClaw AI and the Fabric ecosystem, enabling users to create, search, and organize their digital knowledge base, including notepads, folders, and bookmarks. By utilizing authenticated API calls, it ensures that your workspace data remains synchronized with the AI's actions, facilitating automation of document creation and resource retrieval without requiring manual dashboard access.

Installation

To integrate this skill, ensure you have your Fabric API key ready. Use the following command in your terminal: clawhub install openclaw/skills/skills/tristanmanchester/fabric-api

Once installed, configure your settings by defining the fabric-api entry under your skills configuration. Ensure you map your FABRIC_API_KEY to the apiKey field in your primaryEnv to allow for secure authentication.

Use Cases

• Automated Research Management: Automatically capture research URLs and organize them into specific folders with relevant tags.
• Content Drafting: Generate markdown-based meeting notes or project briefs directly into your Fabric inbox.
• Workflow Integration: Sync data from other OpenClaw tools directly into organized Fabric notepads for long-term storage.
• Knowledge Organization: Programmatically structure your workspace hierarchy by creating nested folders based on project requirements.

Example Prompts

1. "Create a new notepad in my inbox titled 'Q4 Project Plan' with the content: 'Review roadmap and budget constraints' and add tags for 'planning' and 'urgent'."
2. "Search for the folder named 'Design Assets' and create a new bookmark inside it for the URL https://figma.com/design-system."
3. "Save these notes to my Fabric account: 'Ideas for the new marketing campaign include social media outreach and influencer partnerships'. Use the 'Marketing' folder if it exists, otherwise put it in the inbox."

Tips & Limitations

• Hierarchy: Always remember that most endpoints require a parentId. When in doubt, use @alias::inbox to prevent orphaned items.
• Tags: Tag objects must be formatted as { "name": "tag name" } or { "id": "<uuid>" }. Avoid using raw strings or arrays of strings, as this will result in API validation errors.
• Debugging: When testing new configurations, use the --fail-with-body flag in your curl commands. This provides granular feedback on 4xx error codes, helping you identify if you are missing a required field like text or parentId.