# docyrus-platform

A conceptual map of the Docyrus platform: its building blocks, how they fit together, and which dedicated skill to reach for on a given task.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 296 installs · ★ 13 repo stars
- Author: Docyrus
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/Docyrus/agent-skills/tree/HEAD/skills/docyrus-platform/SKILL.md
- Updated: 2026-09-26
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/docyrus-platform

## What it does

The skill lays out how Docyrus is put together and what a project is assembled from. Building blocks get their own section: apps as top-level containers, four kinds of data sources (simple, advanced, external connections to databases or APIs, and ready-made system ones), field types, enumerations, SQL query templates with variables and runtime filters, plus automations that pair a trigger with a chain of action nodes.

Routing is the real job here. Concepts stay in this skill; the work goes to the neighbours it names: `docyrus-data-source-design` for schemas, `docyrus-automation-design` for workflows, `docyrus-cli-app` for terminal commands, `docyrus-api-dev` for query payloads and formulas. Further sections describe the query engine and DSQL, the agent builder, OAuth2 and tenant isolation, connectors, platform services and developer tooling.

It creates no files and no schemas. Concepts only, which is the point: skip the map and you can end up building an automation where a data source schema was needed.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add Docyrus/agent-skills --skill docyrus-platform -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/docyrus-platform/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/docyrus-platform/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add Docyrus/agent-skills --skill docyrus-platform -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/docyrus-platform/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add Docyrus/agent-skills --skill docyrus-platform -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/docyrus-platform/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install Docyrus/agent-skills skills/docyrus-platform
```

2. **Manually: put the files in place**
- File: `.github/skills/docyrus-platform/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add Docyrus/agent-skills --skill docyrus-platform -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/Docyrus/agent-skills --path skills/docyrus-platform
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/docyrus-platform/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add Docyrus/agent-skills --skill docyrus-platform -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/Docyrus/agent-skills/tree/HEAD/skills/docyrus-platform/SKILL.md

## When to use it
- work out which parts make up a Docyrus app
- pick the right skill for a schema or an automation
- tell an external data source apart from a system one
- find the skill that covers DSQL queries or terminal work
- explain the platform layout to a team before a build starts

## Example prompts
- Walk me through the Docyrus platform: how data sources, fields and automations fit together.
- Which skill should I use for a data source schema, and which one for an automation?
- Show me the Docyrus capability map before we start building the app.

## Similar
- [knowledge-base-for-startups](https://affpapa.org/en/nevibecode/skills/knowledge-base-for-startups.md) — skill · 569 installs
- [clariBI.com](https://affpapa.org/en/nevibecode/mcp/claribicom.md) — MCP server · 4431 installs
- [Architecture Intelligence Platform](https://affpapa.org/en/nevibecode/mcp/architecture-intelligence-platform.md) — MCP server · ★ 10 repo stars
- [reddit-search-api](https://affpapa.org/en/nevibecode/skills/reddit-search-api.md) — skill · 13400 installs
- [notion](https://affpapa.org/en/nevibecode/skills/notion.md) — skill · 5700 installs
- [pipefy-automations](https://affpapa.org/en/nevibecode/skills/pipefy-automations.md) — skill · 789 installs

From the same set: [docyrus/agent-skills](https://affpapa.org/en/nevibecode/by/docyrus/agent-skills.md) — 3 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
