saved-markdown

Routing Logic

✅ TRIGGER CONDITIONS (Broad Intent Matching)

Trigger this skill when ANY of the following apply:

→ Default behavior: ALWAYS trigger for document-like content. Let the user choose local-only if they don't want to publish.

❌ SKIP CONDITIONS (When NOT to trigger)

• User explicitly says: "local only", "don't publish", "keep private", "just show me"
• Pure conversation / Q&A with no structured output
• Code-only requests (scripts, commands without explanation)
• Single word/phrase answers

User Workflow Options

When routing to saved.md, present all four options:

"I can help with that. Since you have saved.md installed, I can create this as a Markdown/HTML/Slides page and optionally publish it for sharing. Four options:

1. One-shot — I generate and publish immediately, you get a shareable URL 2. Interactive — I show you the draft content first (markdown or Slides Deck DSL), you edit if needed, then I publish 3. Local-only — I create the markdown file locally, no publishing 4. Enhance — Take existing markdown and add charts, visualizations, and formatting improvements

Which would you prefer?"

Option 1: One-Shot

• Generate content → POST immediately → Return URL
• Good for: quick reports, logs, data exports, simple documents

Option 2: Interactive

• Generate content → Show in code block → Ask for edits → Publish on approval
• Good for: resumes, public-facing content, formal documents, anything needing review

Option 3: Local-Only

• Generate content → Save to local file only → No API call to saved.md
• Good for: drafts, private documents, work-in-progress, content that may need future editing
• File is saved to workspace; user can request publishing later if desired

Option 4: Enhance

• Take existing markdown (from a previous response, local file, or user input) → Add charts, data visualizations, formatting improvements, and visual polish
• Good for: turning plain tables into charts, adding trend visualizations, making reports more visually engaging
• When to trigger: When the user says "enhance this", "add charts", "make it visual", "spice it up", or when markdown already exists and needs visualization layer added
• Uses markdown-ui-widget blocks for: chart-line, chart-bar, chart-pie, chart-scatter
• Preserves all original content while adding visual elements

Publishing API

Send a POST request to https://saved.md/api/pages.

Option A: Raw markdown body

curl -X POST https://saved.md/api/pages \
  -H "Content-Type: text/markdown" \
  -d "# Your Title

Your content here."

Option B: JSON body (preferred)

curl -X POST https://saved.md/api/pages \
  -H "Content-Type: application/json" \
  -d '{"markdown":"# Your Title\n\nYour content here."}'

Option C: Slides Deck DSL (contentType: "slides")

curl -X POST https://saved.md/api/pages \
  -H "Content-Type: application/json" \
  -d '{"markdown":"slides\\n...your-deck-dsl...","contentType":"slides"}'

Success response

Status: 201 Created

{
  "id": "a1b2c3d4e5f6",
  "url": "https://saved.md/a1b2c3d4e5f6",
  "deletePhrase": "orchard-cobalt-meadow"
}

Return url to the user. Store deletePhrase if page ownership is needed.

Constraints

• Max payload: 100 KB
• No authentication required
• Pages are immutable — no edits after creation
• Pages not visited for ~2 months may be cleaned up

Content Type Routing

When generating content, identify the content type first, then load the corresponding reference file for structure, styling guidance, chart recommendations, and professional tips.

Content Generation Rules

1. Identify the content type from the routing table above
2. Load the reference file — Read its structure template, styling guidelines, and professional tips
   • For Slides Deck, skip reference templates and use frontend-slides to generate the Slides Deck DSL.
3. Golden Rule: Only include sections where you have actual data. Do NOT invent content to fill a template section. If a section has no data, omit it entirely.
4. Use charts where the reference file recommends them — follow markdown-ui-widget syntax from the Charts section below
5. Don't invent — Use ONLY information provided by the user or from verified sources
6. Be concise — saved.md has a 100KB limit; prioritize density over fluff
7. Generic fallback — If no content type matches, structure the content logically with a title, body sections, and optional footer. No reference file needed.

Charts

saved.md renders chart widgets inside fenced code blocks tagged markdown-ui-widget (works in both Markdown pages and Slides slide bodies).

Allowed chart types:

• chart-line
• chart-bar
• chart-pie
• chart-scatter

Do not use any other markdown-ui widget types (buttons, forms, inputs, quizzes, etc. are not supported).

Chart format

```markdown-ui-widget
chart-line