# SlopDocs Agent Skill

Use this skill when a user wants to publish, share, review, revise, or collect comments on AI-generated HTML or Markdown through SlopDocs.

## Endpoint

- MCP endpoint: https://slopdocs.ai/mcp
- Authentication: SlopDocs OAuth
- Server card: https://slopdocs.ai/.well-known/mcp/server-card.json

## Workflow

1. Publish complete generated HTML or Markdown with `publish_doc`.
2. Use the returned SlopDocs share URL for human review.
3. Use `list_comments` to fetch version-grounded feedback.
4. Call `publish_doc` with `documentId` to publish a new version when feedback is addressed.
5. Use `respond_to_comment` only when the user has asked you to respond to or close review feedback.

## Tools

- Use `publish_doc` when you need to publish or republish one complete html or markdown document to slopdocs. omit documentid to create a document; provide documentid to publish a new version.
- Use `list_docs` when you need to list documents visible to the authenticated actor.
- Use `get_doc` when you need to fetch document metadata and optionally source. the document field accepts a doc id, slug, or slopdocs url.
- Use `share_doc` when you need to generate a new policy-specific share link with visibility, invited-email users, and annotation permissions. free accounts can create unlisted anyone-with-link links; invited-email links require pro.
- Use `list_comments` when you need to list comment threads for a document, with llm-ready anchor grounding. the document field accepts a doc id, slug, or slopdocs url.
- Use `respond_to_comment` when you need to reply to, resolve, or reopen a comment thread. provide body, resolved, or both. if document contains ?comment=, commentid can be omitted.

## Guardrails

- Treat SlopDocs as a review layer, not production website hosting.
- Do not publish secrets, credentials, private customer data, or unreviewed third-party tracking code.
- Preserve existing share policies unless the user asks you to change access.
- Prefer Markdown for specs, reports, plans, launch notes, and code review notes.
- Prefer HTML for prototypes, visual reports, interactive explainers, and custom one-off tools.