
docyrus-platform
Architecture and building-blocks reference for the Docyrus platform — what the platform is made of (apps, data sources, fields, enumerations, custom queries, automations) and how the pieces fit together. Use when you need conceptual context about how Docyrus works, what its building blocks and capabilities are, or to decide which dedicated skill to use for a task. This is the conceptual map and router; hands-on how-to lives in the dedicated design / CLI / API skills it points to (data sources, automations, agents, AI tools, templates, webforms, ACL, querying, the CLI, and the REST API).
- Installs
- 222
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/docyrus/agent-skills --skill docyrus-platform- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads docyrus-platform automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Docyrus Platform
Docyrus is an AI-native Backend Platform as a Service (BPaaS) for building B2B web/mobile apps, client portals, internal tools, AI agents, chatbots, and integrations — without building backend infrastructure from scratch. This skill is the architecture map: the building blocks, how they fit, and which dedicated skill owns each how-to.
Core Building Blocks
The platform is composed of building blocks that compose into apps:
- Apps — Top-level containers that group data sources, automations, agents, and custom queries into a deployable unit.
- Data Sources — Structured collections of records with typed schemas. Four types: simple, advanced, external (connected DBs/APIs), and system (pre-built). Every data source — internal or external — is exposed through one unified CRUD endpoint.
- Fields — 45+ field types defining each data source's schema: text, numbers, dates, selections, relations, files, formulas, nested data, and more.
- Enumerations — Reusable option sets for selection fields (color, icon, ordering).
- Custom Queries — SQL-based analytics templates with variable interpolation, runtime filters, and multi-database targeting.
- Automations — Event-driven workflows: triggers (record changes, schedule, webhook, email, webform, button) → action-node chains (email, notifications, record ops, HTTP, AI, scripts).
Detailed building-block specifications: references/core-building-blocks.md.
Which skill for which task
This skill holds the concepts. For doing the work, use the dedicated skill:
| To… | Use skill |
|---|---|
| Design a data source (schema, fields, relations, enums, access) | docyrus-data-source-design |
| Build an automation (triggers + action-node graph) | docyrus-automation-design |
| Build a custom AI agent + its sub-resources | docyrus-agent-design |
| Author AI tools the system base agent ("Docy") calls | docyrus-app-ai-tools |
| Design an email template | docyrus-email-template-design |
| Design an HTML/PDF print/report template | docyrus-print-pdf-template-design |
| Build a public webform that collects submissions into records | docyrus-webform-design |
| Design a data source's record create/edit/view form (grid, sections, conditional rules) | docyrus-dynamic-form-design |
| Configure tenant ACL (roles, hierarchy units, role rules) | docyrus-acl-design |
Discover & call third-party integrations/connectors (docyrus connect) | docyrus-integrations-and-connectors |
| Query/CRUD data, write filters/formulas, build query payloads | docyrus-api-dev |
Write DSQL (logical SQL) queries, or natural-language dsql ask | docyrus-dsql-query-design |
| Drive everything from the terminal (auth, ds, studio, automation, agent, …) | docyrus-cli-app |
| Build a React app on Docyrus (collections, grids, forms) | docyrus-app-dev-react, docyrus-data-grid-page-design, docyrus-record-detail-form-design |
Capability areas (concepts)
Querying & Data Operations
Unified query engine: column selection, 50+ filter operators, aggregations, formulas, pivots, child queries, full-text search; full CRUD with bulk ops, comments, and attachments; plus a read-only logical SQL endpoint (DSQL) over appSlug.dataSourceSlug tables. Concept overview: references/querying-and-data-operations.md.
→ Query payloads & formulas: docyrus-api-dev. DSQL (logical SQL, dsql ask): docyrus-dsql-query-design. Terminal querying: docyrus-cli-app.
AI Capabilities
AI agent builder with tool binding, knowledge bases, MCP servers, 18+ model providers, agent chaining, task scheduling, persistent memory, chat integrations, and evaluation metrics. Concept overview: references/ai-capabilities.md. → Build agents: docyrus-agent-design. Author the tools Docy calls: docyrus-app-ai-tools.
Automation & Workflows
Event-driven automation engine: trigger types and action-node types, conditional flows, action chains, archiving. Concept overview: references/automation-and-workflows.md. → Build automations: docyrus-automation-design.
Authentication & Multi-Tenancy
OAuth2 flows (PKCE, Client Credentials, Device Code), scope-based permissions, tenant isolation, role-based and record-level ACL, React auth helpers, and the client portal. Concept overview: references/auth-and-multi-tenancy.md. → Configure ACL: docyrus-acl-design. OAuth in app code: docyrus-api-dev.
Integrations & Events
Connector framework for HTTP and SQL providers, webhook/event management, connector discovery, collaborative document editing, in-app messaging, notifications, and email. Concept overview: references/integrations-and-events.md.
→ Discover & use connectors (docyrus connect): docyrus-integrations-and-connectors. Webhook/messaging CLI: docyrus-cli-app.
Platform Services
App templates, data import/export, reporting & analytics, deployment & versioning, localization & navigation, audit logging, and billing. Concept overview: references/platform-services.md. → Public data-collection webforms are their own skill: docyrus-webform-design.
Developer Tools
Auto-generated OpenAPI specs, MCP server, a full-featured CLI, REST API client libraries, a React auth provider, and auto-generated collection hooks. Concept overview: references/developer-tools.md.
→ Full CLI command index: docyrus-cli-app (docyrus <cmd> --help for flags). REST client + query payloads + formulas: docyrus-api-dev.
FAQ
What does the docyrus-platform skill do?
Architecture and building-blocks reference for the Docyrus platform — what the platform is made of (apps, data sources, fields, enumerations, custom queries, automations) and how the pieces fit together. Use when you need conceptual context about how Docyrus works, what its building blocks and capabilities are, or to decide which dedicated skill to use for a task. This is the conceptual map and router; hands-on how-to lives in the dedicated design / CLI / API skills it points to (data sources, automations, agents, AI tools, templates, webforms, ACL, querying, the CLI, and the REST API).
How do I install docyrus-platform?
Run npx skills add https://github.com/docyrus/agent-skills --skill docyrus-platform in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/docyrus-platform/ (personal) or .claude/skills/docyrus-platform/ (project).
Which AI agents can use docyrus-platform?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is docyrus-platform safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains docyrus-platform?
It is published by docyrus in docyrus/agent-skills. It has 222 recorded installs.
More from docyrus/agent-skills
docyrus-api-dev
docyrus/agent-skills
Develop applications using the Docyrus API with @docyrus/api-client and @docyrus/signin libraries. Use when building apps that authenticate with Docyrus OAuth2 (PKCE, iframe, client credentials, device code), make REST API calls to Docyrus data source endpoints, construct query payloads with filters, aggregations, formulas, pivots, and child queries, or integrate with external connectors (discover connectors, send requests through provider auth, run actions). Triggers on tasks involving Docyrus API integration, @docyrus/api-client usage, @docyrus/signin authentication, data source query building, Docyrus REST endpoint consumption, connector discovery, or external provider requests.
docyrus-cli-app
docyrus/agent-skills
Use the Docyrus CLI (docyrus) to interact with the Docyrus platform from the terminal. Use when the user asks to authenticate, list apps, query or manage data records (ds), manage dev app data source schema objects (studio) including data sources, fields, enums, data views, forms, webforms, HTML/PDF export templates, and email templates, manage automations and their triggers/action nodes (automation), build or edit custom AI agents and their sub-resources (agent), set an app's AI agent context or manage app-scoped AI tools (apps), list tenant email accounts and send emails (messaging), manage tenant account settings — brands, the current user's profile, and tenant regional/formatting preferences (account), discover and call connectors (connect), send API requests, switch tenants/accounts, discover tenant OpenAPI specs, drive browser automation (browser), chat with platform agents (docy), launch the pi cowork/coding agents (worky/cody/coder), run the agent br
docyrus-api-doctor
docyrus/agent-skills
Run after making Docyrus API changes to catch bugs, performance issues, and code quality problems. Use when implementing or modifying code that uses Docyrus collection hooks (.list, .get, .create, .update, .delete), direct RestApiClient calls, query payloads with filters/calculations/formulas/childQueries/pivots, or TanStack Query integration with Docyrus data sources. Triggers on tasks involving Docyrus API logic, data fetching, mutations, or query payload construction.
docyrus-app-dev
docyrus/agent-skills
Build React TypeScript web applications using Docyrus as a backend. Use when creating or modifying apps that authenticate with Docyrus OAuth2, fetch/mutate data via the @docyrus/api-client library, use auto-generated collections for CRUD operations, or build queries with filters, aggregations, formulas, pivots, and child queries against Docyrus data sources. Triggers on tasks involving @docyrus/api-client, @docyrus/signin, Docyrus collections, data source queries, or Docyrus-backed React app development.
docyrus-architect
docyrus/agent-skills
Open the skill to read its SKILL.md instructions.
docyrus-app-ui-design
docyrus/agent-skills
Open the skill to read its SKILL.md instructions.
Popular backend & apis skills
find-skills
vercel-labs/skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
entra-app-registration
microsoft/azure-skills
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.
google-agents-cli-adk-code
google/agents-cli
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).
embedded-captions
heygen-com/hyperframes
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
entra-agent-id
microsoft/azure-skills
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).
neon
neondatabase/agent-skills
Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.