|

Skill: Creating FluentMCP Skill Documentation

Skill: Creating FluentMCP Skill Documentation

Need to document a new FluentMCP skill? Your AI assistant can create professional, consistent documentation that helps both humans and other AI assistants understand how to use the skill.

The Problem

When you create a new automation or workflow using FluentMCP, you need documentation that serves two audiences: humans who want to understand what it does and why, and AI assistants that need compressed technical instructions to execute it.

Why this matters: Without proper documentation, skills become “tribal knowledge” that only you understand. Good documentation makes your skills reusable, shareable, and accessible to your entire team or community.

The Solution

Your AI assistant can generate complete skill documentation following the FluentMCP template. Just tell it what skill you want to document, and it will create a professional page with all the right sections, styling, and structure.

Simple request example:

“Create skill documentation for [skill name] that explains [what it does]”

The AI will generate a fully-formatted page with human-friendly explanations and an LLM-optimized technical reference section, then publish it to your FluentMCP site.

Why This Works

The FluentMCP skill documentation template is designed with a specific structure that works for both audiences:

  1. Human-friendly sections: Clear explanations of the problem, solution, and use cases written for beginners
  2. Consistent structure: Every skill doc follows the same pattern, making them easy to scan and understand
  3. LLM-optimized reference: Compressed technical instructions that AI assistants can quickly parse and execute
  4. Copy functionality: Buttons to copy instructions or share URLs make it easy to use

The template uses custom CSS and HTML wrapped in WordPress’s HTML block format, giving you complete control over the layout while maintaining consistency across all skill documentation.

When To Use

Create skill documentation whenever you have a reusable automation or workflow:

  • New automation workflows: Document multi-step processes that others might want to replicate
  • Complex integrations: Explain how different tools work together
  • Team knowledge sharing: Make your personal workflows available to your team
  • Community contributions: Share useful skills with the FluentMCP community
  • Client deliverables: Provide documentation for custom automations you build for clients

What You’ll Need

Prerequisites:
  • FluentMCP plugin: Installed on your WordPress site
  • AI assistant: Claude (Cursor), ChatGPT, or similar with MCP support
  • Skill knowledge: Understanding of what the skill does and how it works
  • Example use cases: Real-world scenarios where the skill is useful

That’s all you need. The AI handles all the formatting, structure, and technical details.

How To Ask Your AI

You can request skill documentation in natural language. Here are some examples:

Basic request:

“Create skill documentation for bulk uploading images to WordPress media library”

More detailed request:

“Document the skill for creating FluentCommunity posts with AI-generated content. Include examples of how to specify tone, length, and topic.”

With specific sections:

“Create skill docs for the screenshot automation. Make sure to explain why scrollbars are a problem and include troubleshooting for Chrome path issues.”

The Documentation Structure

Every skill document follows this exact structure:

1. The Problem

Explains what issue this skill solves and why it matters to users.

2. The Solution

Describes how the AI assistant handles the task automatically.

3. Why This Works

Behind-the-scenes explanation of the technical approach (written for beginners).

4. When To Use

Specific use cases and scenarios where this skill is valuable.

5. What You’ll Need

Prerequisites and requirements (tools, plugins, accounts, etc.).

6. How To Ask Your AI

Example prompts showing different ways to request the skill.

7. Common Issues

Troubleshooting section with “What this means” and “How to fix” explanations.

8. For AI Assistants: Technical Reference

Compressed, LLM-optimized instructions with copy buttons for easy sharing.

Common Issues

AI creates generic documentation

What this means: The AI doesn’t have enough specific information about your skill.

How to fix: Provide more details: “The skill uses [specific tools] to accomplish [specific task]. Include examples like [example 1] and [example 2].”

Formatting looks wrong

What this means: The HTML block wrapper might be missing or incorrect.

How to fix: Make sure the content is wrapped in <!-- wp:html --> and <!-- /wp:html --> tags.

Sidebar navigation doesn’t work

What this means: The section IDs in the HTML don’t match the links in the table of contents.

How to fix: Ask the AI: “Fix the navigation links so they match the section IDs.”

For AI Assistants: Technical Reference

This section contains compressed instructions optimized for AI assistants. If you’re a human, you can copy this text or share the URL with your AI to help it execute this skill.

SKILL: Create FluentMCP Skill Documentation TASK: Generate professional skill documentation with human and LLM sections COMPLEXITY: Intermediate (requires content creation + WordPress publishing) TOOLS REQUIRED: – create_content (FluentMCP WordPress) STRUCTURE (8 required H2 sections): 1. The Problem – What issue does this solve? Why does it matter? 2. The Solution – How does AI assistant handle it? Plain English explanation 3. Why This Works – Technical explanation for beginners (tools, process, automation) 4. When To Use – Specific use cases (bullet list with bold labels) 5. What You’ll Need – Prerequisites in callout-warning box 6. How To Ask Your AI – Example prompts in callout-info boxes 7. Common Issues – H3 subheadings with “What this means” and “How to fix” 8. For AI Assistants: Technical Reference – LLM-optimized compressed instructions SIDEBAR COMPONENTS: – Table of Contents (links to all H2 sections with matching IDs) – LLM Quick Access box (dark gray, buttons for View Instructions and Copy URL) CSS REQUIREMENTS: – Sidebar sections: background #f6f6f6, border 2px solid var(–gray-200) – TOC links: color #222, font-size 1rem – LLM quick access: border 2px solid var(–gray-800) – Hyphenation: hyphens: auto on h1, h2, p elements – Two-column layout: main content (flex: 1) + sidebar (280px, sticky) CONTENT GUIDELINES: – Write for complete beginners – explain everything in plain English – Focus on what AI does FOR user, not what user must do manually – Use callout boxes: callout-info (examples), callout-warning (prerequisites) – LLM section: compressed technical format with tool names, parameters, workflow steps – NO footer section at bottom FORMAT: Wrap entire content in:
[ML Canvas mode CSS] [Full CSS from template] [HTML structure with doc-wrapper, doc-main, doc-sidebar] [JavaScript for copy buttons]
JAVASCRIPT (required for copy buttons): – Copy target content by data-copy-target attribute – Copy URL with hash by data-copy-url attribute – Copy full page URL by data-copy-url-full attribute – Show “Copied!” feedback for 2 seconds PUBLISH: Use create_content tool with content_type=”post”, status=”publish” Always provide clickable link after publishing