Reference

learn_marcora_tools

Returns Marcora's guide to its own tools: what each Marcora object is, which tool fits which request, the order the tools chain in, and the mistakes to avoid.

Parameters

Name	Type	Required	Default	Description
`topic`	`string`	No	—	Which section of the guide to return. Omit it for the overview, which lists every topic with a summary — then pass the topic whose summary matches the task (e.g. `workflows` before building a Marcora workflow, `projects-and-briefs` before working inside a project). One of: choosing-tools, generate-content, projects-and-briefs, add-context, find-context, grounding, workflows, plans-and-playbooks, pitfalls, edge-cases, recipes, glossary.

Input Schema

{
  "type": "object",
  "properties": {
    "topic": {
      "enum": [
        "choosing-tools",
        "generate-content",
        "projects-and-briefs",
        "add-context",
        "find-context",
        "grounding",
        "workflows",
        "plans-and-playbooks",
        "pitfalls",
        "edge-cases",
        "recipes",
        "glossary"
      ],
      "type": "string",
      "description": "Which section of the guide to return. Omit it for the overview, which lists every topic with a summary — then pass the topic whose summary matches the task (e.g. `workflows` before building a Marcora workflow, `projects-and-briefs` before working inside a project)."
    }
  }
}

Output Schema

{
  "type": "object",
  "required": [
    "topic",
    "title",
    "guide_version",
    "content",
    "topics"
  ],
  "properties": {
    "title": {
      "type": "string",
      "description": "Human-readable title of the section."
    },
    "topic": {
      "type": "string",
      "description": "The section returned: `overview`, or the topic that was requested."
    },
    "topics": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "topic",
          "title",
          "summary"
        ],
        "properties": {
          "title": {
            "type": "string",
            "description": "Title of the topic."
          },
          "topic": {
            "type": "string",
            "description": "Value to pass as `topic`."
          },
          "summary": {
            "type": "string",
            "description": "One line on what the topic covers, to decide whether the task needs it."
          }
        }
      },
      "description": "Every topic in the guide, in order. Pass one as `topic` to read that section."
    },
    "content": {
      "type": "string",
      "description": "The section's guidance, in markdown."
    },
    "guide_version": {
      "type": "string",
      "description": "Version of the Marcora guide this text comes from (matches the companion marcora-mcp skill's version)."
    }
  }
}

Instructions

Returns Marcora's guide to its own tools: what each Marcora object is, which tool fits which request, the order the tools chain in, and the mistakes to avoid.

When to use this tool: call it once before multi-step Marcora work the user has asked for — for example generating content into a project, setting a project brief, adding reference context, building a workflow, or producing a content plan — or whenever you are unsure which Marcora tool fits a request or how two of them chain. If the Marcora skill is already loaded in your context, you don't need this tool: it holds the same guidance.

Called with no topic, it returns an overview (the object model, the context model, a which-tool table) and the list of topics, each with a one-line summary. Call it again with topic for the one section the task needs; don't fetch every topic.

Read-only: it reads no workspace data, changes nothing, and uses no credits.

Parameters

Parameter	Type	Required	Description
`topic`	string	No	Which section of the guide to return. Omit it for the overview, which lists every topic with a summary — then pass the topic whose summary matches the task (e.g. `workflows` before building a Marcora workflow, `projects-and-briefs` before working inside a project). One of: `choosing-tools`, `generate-content`, `projects-and-briefs`, `add-context`, `find-context`, `grounding`, `workflows`, `plans-and-playbooks`, `pitfalls`, `edge-cases`, `recipes`, `glossary`

Topics

Topic	Covers
`choosing-tools`	The full which-tool table with the reason for each choice: documents vs context items, briefs, editing, refreshing web pages, search vs browse, Brand Foundation, teams.
`generate-content`	Workflow 1: generating a document, with or without a blueprint, a project or targeting; sync vs async; when (not) to pre-fetch context.
`projects-and-briefs`	Workflows 2 and 4: creating a project, setting or editing its brief, and reading the brief before working inside a project.
`add-context`	Workflow 3: saving reference material to the Reference Library or a project (pasted text, a one-off URL snapshot, or a refreshable web page).
`find-context`	Workflow 5: RAG search vs browsing vs semantic ranking, and grounding a draft you write yourself in the team's brand and library.
`grounding`	Workflow 6: checking a document's claims against the team's context, polling, coverage, and applying fixes safely.
`workflows`	Building, activating, scheduling and running Marcora workflows; output destinations; dedup; run summaries; risks.
`plans-and-playbooks`	The plans board stage machine, visibility, the plan and playbook tools, and producing a plan into content.
`pitfalls`	The high-frequency mistakes (links, duplicates, pre-fetching, polling, mutually exclusive inputs) and what each error message means.
`edge-cases`	Detailed symptoms, causes and fixes for unusual results: missing briefs, chunk-only context, pagination, new-account setup, workflow state, Brand Foundation links.
`recipes`	Blueprint creation, Blueprint Exchange imports, async follow-up, external sharing, Word export, project rename/archive, Brand Foundation read/update.
`glossary`	One-line definitions of every Marcora object.

Output

Field	Type	Description
`topic`	string	The section returned: `overview`, or the topic that was requested.
`title`	string	Human-readable title of the section.
`guide_version`	string	Version of the Marcora guide this text comes from (matches the companion marcora-mcp skill's version).
`content`	string	The section's guidance, in markdown.
`topics`	array	Every topic in the guide, in order. Pass one as `topic` to read that section.

Errors. An unrecognised topic returns a readable error listing the valid topics.

Example prompts

"Before you start, check how Marcora's tools fit together"
"Which Marcora tool should I use to set a project brief?"

Examples

Read the guide section on project briefs

Before setting a project brief, the assistant fetches the one guide topic that covers projects and briefs.

Input

{
  "topic": "projects-and-briefs"
}

Output

{
  "topic": "projects-and-briefs",
  "title": "Projects and project briefs",
  "guide_version": "0.7.13",
  "content": "### Workflow 4 — Create a project\n\n...",
  "topics": [
    {
      "topic": "choosing-tools",
      "title": "Choosing between similar tools",
      "summary": "The full which-tool table with the reason for each choice: documents vs context items, briefs, editing, refreshing web pages, search vs browse, Brand Foundation, teams."
    },
    {
      "topic": "generate-content",
      "title": "Generate content",
      "summary": "Workflow 1: generating a document, with or without a blueprint, a project or targeting; sync vs async; when (not) to pre-fetch context."
    },
    {
      "topic": "projects-and-briefs",
      "title": "Projects and project briefs",
      "summary": "Workflows 2 and 4: creating a project, setting or editing its brief, and reading the brief before working inside a project."
    },
    {
      "topic": "add-context",
      "title": "Add reference context",
      "summary": "Workflow 3: saving reference material to the Reference Library or a project (pasted text, a one-off URL snapshot, or a refreshable web page)."
    },
    {
      "topic": "find-context",
      "title": "Find existing context and answer questions",
      "summary": "Workflow 5: RAG search vs browsing vs semantic ranking, and grounding a draft you write yourself in the team's brand and library."
    },
    {
      "topic": "grounding",
      "title": "Ground a document against the library",
      "summary": "Workflow 6: checking a document's claims against the team's context, polling, coverage, and applying fixes safely."
    },
    {
      "topic": "workflows",
      "title": "Workflows (reusable multi-step processes)",
      "summary": "Building, activating, scheduling and running Marcora workflows; output destinations; dedup; run summaries; risks."
    },
    {
      "topic": "plans-and-playbooks",
      "title": "Content plans and playbooks",
      "summary": "The plans board stage machine, visibility, the plan and playbook tools, and producing a plan into content."
    },
    {
      "topic": "pitfalls",
      "title": "Pitfalls, conventions and error runbook",
      "summary": "The high-frequency mistakes (links, duplicates, pre-fetching, polling, mutually exclusive inputs) and what each error message means."
    },
    {
      "topic": "edge-cases",
      "title": "Edge cases",
      "summary": "Detailed symptoms, causes and fixes for unusual results: missing briefs, chunk-only context, pagination, new-account setup, workflow state, Brand Foundation links."
    },
    {
      "topic": "recipes",
      "title": "Long-tail recipes",
      "summary": "Blueprint creation, Blueprint Exchange imports, async follow-up, external sharing, Word export, project rename/archive, Brand Foundation read/update."
    },
    {
      "topic": "glossary",
      "title": "Glossary",
      "summary": "One-line definitions of every Marcora object."
    }
  ]
}