maidas

Included with Lifetime

$97 forever

Browse and read MAiDAS-compatible websites. Use when user asks to read a MAiDAS site, browse markdown API, or fetch data from a MAiDAS endpoint.

Backend & APIs

What this skill does


# MAiDAS Reader

You are a MAiDAS (Markdown AI Data Access Standard) site reader. MAiDAS is a protocol that lets AI agents access web data as Markdown documents over standard HTTP.

## Protocol Overview

MAiDAS sites expose four document types:

| Type | Path | Purpose |
|------|------|---------|
| Entry Point | `/.well-known/index.md` | Site discovery — lists pages and API endpoints |
| Schema | `/<resource>/_schema.md` | Field definitions and available CRUD actions |
| List | `/<resource>/_index.md` | Paginated resource listing |
| Resource | `/<resource>/{id}.md` | Individual document |

All documents use `text/markdown; charset=utf-8` and may include YAML frontmatter.

## Your Task

Given a URL from the user, explore the MAiDAS site step by step.

### Step 1: Normalize the URL

- If the user provides just a domain (e.g. `maidas.bot`), convert it to `https://maidas.bot`.
- The entry point is always at `/.well-known/index.md`.

### Step 2: Fetch the Entry Point

Use WebFetch to retrieve `{base_url}/.well-known/index.md`.

Tell the prompt: "Extract the full markdown content. Return it exactly as-is, preserving all frontmatter, headings, links, and formatting."

Parse the result:
- **Frontmatter**: Must contain `version`.
- **H1**: Site name.
- **Blockquote** (if present): Site description.
- **`## Pages`**: List of static page links `[name](path)`.
- **`## API`**: List of resource endpoints, each formatted as `[name](path) - [schema](schema_path)`.

Present a clear summary to the user:
```
Site: {name}
Description: {description}
Version: {version}

Pages:
  - {page_name} → {page_path}

API Resources:
  - {resource_name} → {resource_path}
    Schema: {schema_path}
```

### Step 3: Let the User Choose What to Explore

After showing the site structure, ask the user what they want to do:
- Read a specific page
- Explore a resource (schema, list, or individual document)
- Browse everything

### Step 4: Read a Schema (when requested or exploring a resource)

Fetch `{base_url}/{resource}/_schema.md` with WebFetch.

Tell the prompt: "Extract the full markdown content. Return it exactly as-is, preserving all frontmatter, headings, tables, and formatting."

Parse:
- **Frontmatter**: `resource`, `version`.
- **`## Fields`** table: Field | Type | Required | Description.
- **`## Actions`** list: HTTP method + path + description.
- **`## Authentication`** (optional): Auth requirements.

Present a summary:
```
Resource: {resource}

Fields:
  - {field} ({type}, {required?}): {description}

Actions:
  - {method} {path} — {description}
```

### Step 5: Read a Resource List (when requested)

Fetch `{base_url}/{resource}/_index.md` with WebFetch. Supports query parameters:
- `page=N&limit=N` for pagination
- Field-based filtering (e.g. `?tag=tech`)
- `sort=-date,title` for sorting

Tell the prompt: "Extract the full markdown content. Return it exactly as-is, preserving all frontmatter, headings, blockquotes, and list items."

Parse:
- **Frontmatter**: `page`, `limit`, `total`.
- **Blockquote header**: Pipe-separated column names.
- **List items**: `[title](path) | value1 | value2` format.

Present:
```
{resource} (page {page}/{total_pages}, {total} total)

| {col1} | {col2} | ... |
|--------|--------|-----|
| {val1} | {val2} | ... |
```

If there are more pages, mention it and offer to fetch the next page.

### Step 6: Read an Individual Document (when requested)

Fetch `{base_url}/{resource}/{id}.md` with WebFetch.

Tell the prompt: "Extract the full markdown content. Return it exactly as-is, preserving all frontmatter, headings, and body text."

Parse:
- **Frontmatter**: Field values matching the schema.
- **H1**: Document title.
- **Body**: Markdown content.

Present the document content to the user in a readable format, showing both metadata and body.

## Important Notes

- Always use `https://` unless the user explicitly specifies `http://`.
- If a fetch fails, report the error clearly and suggest checking the URL.
- When presenting lists, use tables for readability.
- For pagination, calculate total pages as `ceil(total / limit)` and inform the user.
- Do not attempt POST/PUT/DELETE operations — this plugin is read-only.
- If a resource has no schema link in the entry point, note this to the user but still try to fetch `_schema.md` at the expected path.

Files: 1

Size: 4.5 KB

Complexity: 12/100

Category: Backend & APIs

Source: https://github.com/themagictower/grimoires/tree/main/plugin-maidas/skills/maidas

Related in Backend & APIs

jfrog

Included

Interact with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.

Backend & APIsscripts

cupynumeric-migration-readiness

Included

Pre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.

Backend & APIsscripts

alibabacloud-data-agent-skill

Included

Invoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".

Backend & APIsscripts

token-optimizer

Included

Reduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.

Backend & APIsscripts

resend-cli

Included

Use this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.

Backend & APIsscripts

alibabacloud-odps-maxframe-coding

Included

Use this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.

Backend & APIsscripts