Skills Library

Writing

Writing Studio

Draft and revise sourced private articles with citations and visuals while publishing stays in Prism.

What this skill teaches

A private draft whose argument, evidence, and source trail remain inspectable.

The title lives in the draft title field and the body uses readable structured content.

Images and artifacts land at intentional markers instead of being appended unpredictably.

Workflow

  1. 1

    Retrieve the relevant Project evidence and outline the argument before writing.

  2. 2

    List drafts, then read the full selected draft before revising it, or create a new private draft.

  3. 3

    For generated prose, use contentText Markdown and pass the latest expectedUpdatedAt on updates.

  4. 4

    Attach important sources to the draft evidence trail.

  5. 5

    For planned visuals, add stable markers, upload or create the visual, then replace the marker with insert_article_visual_block.

  6. 6

    Re-read the draft after structural or visual edits and hand publishing back to the user in Prism.

Tool routing

Select the right draft and read its latest complete body before editing.

Create or revise private prose with concurrency protection.

Connect source logs, claims, Project files, documents, or URLs to the draft.

Place covers and inline visuals intentionally without rewriting unrelated body content.

Safety boundaries

  • Draft tools cannot publish, schedule, delete, send subscriber email, or update an already published post.
  • Use force true only for an explicit one-writer agent workflow. Otherwise keep expectedUpdatedAt concurrency checks.
  • Do not rewrite the user's voice or remove user-authored sections unless asked.

SKILL.md source

Public Markdown you can inspect, copy, download, or adapt.

---
name: prism-writing-studio
description: "Use when an AI client needs to create or revise a private Prism article draft from Project evidence while keeping publishing under user control."
---

# Writing Studio

Draft and revise sourced private articles with citations and visuals while publishing stays in Prism.

## Before you start

Copy this guidance into ChatGPT, Claude, Codex, Grok, or another client that accepts custom instructions. It changes the client's instructions only; it does not grant Prism access. Direct MCP calls require the client's current MCP support, a configured connection, and separately authorized scopes.

Scopes this workflow may need:

- `knowledge:read`
- `drafts:read`
- `drafts:write`

The installed skill does not grant these permissions. Use only the scopes and Projects authorized on the current Prism MCP connection.

## Workflow

1. Retrieve the relevant Project evidence and outline the argument before writing.
2. List drafts, then read the full selected draft before revising it, or create a new private draft.
3. For generated prose, use contentText Markdown and pass the latest expectedUpdatedAt on updates.
4. Attach important sources to the draft evidence trail.
5. For planned visuals, add stable markers, upload or create the visual, then replace the marker with insert_article_visual_block.
6. Re-read the draft after structural or visual edits and hand publishing back to the user in Prism.

## Tool routing

- `get_article_drafts`, `get_article_draft_for_edit`: Select the right draft and read its latest complete body before editing.
- `create_article_draft`, `update_article_draft`: Create or revise private prose with concurrency protection.
- `attach_article_source`: Connect source logs, claims, Project files, documents, or URLs to the draft.
- `upload_article_image`, `insert_article_visual_block`: Place covers and inline visuals intentionally without rewriting unrelated body content.

## Expected result

- A private draft whose argument, evidence, and source trail remain inspectable.
- The title lives in the draft title field and the body uses readable structured content.
- Images and artifacts land at intentional markers instead of being appended unpredictably.

## Boundaries

- A skill does not grant Prism access. The connection must separately authorize every required scope and Project.
- Call only tools verified callable by the current AI host. Use discover_prism_actions for granular actions. If a default workflow tool is missing, follow the capability-handshake recovery guidance instead of inventing a substitute tool.
- Read before writing. Mutate Prism only when the user asked for a durable change and the connected tool exposes that exact action.
- Keep retrieved evidence separate from analysis. Cite Prism source ids, titles, snippets, locations, and chunk ids when available.
- Draft tools cannot publish, schedule, delete, send subscriber email, or update an already published post.
- Use force true only for an explicit one-writer agent workflow. Otherwise keep expectedUpdatedAt concurrency checks.
- Do not rewrite the user's voice or remove user-authored sections unless asked.