Our review
Reads and writes pages and cards in a Quicks workspace via its external JSON API, leveraging an authentication token embedded in the URL.
Strengths
- Simple authentication: token is embedded in the URL, no extra headers needed.
- Full CRUD for pages and cards, including Markdown notes support.
- Automatic detection and saving of the base URL for reuse across sessions.
Limitations
- Requires internet access and an active Quicks API endpoint.
- Tied to Quicks' specific URL format (/api/x/), not general-purpose.
- Paths may include non-ASCII characters, which could cause encoding issues.
Use this skill when you need to programmatically interact with a Quicks workspace, such as syncing notes, automating card creation, or integrating external data.
Avoid using this skill for other content management platforms or when you need standard REST API authentication with custom headers.
Security analysis
SafeThe skill only describes an HTTP API via WebFetch; no destructive commands, exfiltration, or obfuscation are present. The use of an embedded token in the URL is a standard API pattern, and the skill does not instruct the agent to expose it to third parties.
No concerns found
Examples
Create a new page called 'Meeting Notes' under the parent page 'Work' in my Quicks workspace.Add a notes card to the page 'Project Alpha' with the text '# Status Update
- Completed task A
- Started task B'.Show me all pages in my Quicks workspace.name: quicks-api description: > Interact with Quicks workspace via the external JSON API. Use when the user provides a quicks.ai URL (contains /api/x/), asks to read/write workspace pages or cards, or wants to give an LLM access to their workspace data. allowed-tools: WebFetch
Quicks Workspace API
JSON API for reading and writing pages with cards. Auth token is embedded in the URL — no headers needed.
Token resolution
On every invocation, resolve the base URL in this order:
- User provided a URL (contains
/api/x/) → extract base URL, save to~/.quicks/token.json - File
~/.quicks/token.jsonexists → read and usebaseUrlfrom it - Neither → ask the user to get their API URL at https://3.quicks.ai/account
Token file format (~/.quicks/token.json)
{ "baseUrl": "https://api-3.quicks.ai/api/x/abc123-..." }
Endpoints
All endpoints use {base} = the baseUrl from token. Paths may contain non-ASCII (Cyrillic). Use paths exactly as returned by GET {base}.
Pages
| Method | Path | Body | Response |
|--------|------|------|----------|
| GET | {base} | — | { widgets, pages } — list all pages and schemas |
| GET | {base}/pages/{path} | — | { page, cards } — read page with all cards |
| PUT | {base}/pages/{path} | { cards: [{ id, data }] } | { ok } — update cards |
| POST | {base}/pages | { parentPath?, slug, name } | { path } — create page |
Cards
| Method | Path | Body | Response |
|--------|------|------|----------|
| POST | {base}/pages/{path}/cards | { type, name?, data? } | { id } (201) — create card |
| DELETE | {base}/pages/{path}/cards/{cardId} | — | { ok } — delete card |
Notes (markdown shortcuts)
| Method | Path | Body | Response |
|--------|------|------|----------|
| POST | {base}/pages/{path}/notes | { name?, text } | { id } (201) — create notes card |
| GET | {base}/pages/{path}/notes/{cardId} | — | { id, name, text } — read notes |
| PUT | {base}/pages/{path}/notes/{cardId} | { text } | { ok } — update notes |
Tips
type: "text"= long markdown content,type: "string"= short value- Card
statusis read-only:"empty"|"processing"|"done"|"error" - Errors: 401 = bad token, 404 = page/card not found, 400 = validation error
- Before adding content, read the page first to check for duplicates
Task Prioritizer
Productivity
Prioritizes your tasks using Eisenhower, ICE, and RICE frameworks.
Weekly Status Report Generator
Productivity
Generate structured and concise weekly status reports.
Daily Standup Report
Productivity
Generates structured and concise daily standup reports.