Diataxis Writing
PassAudited by ClawScan on May 1, 2026.
Overview
This appears to be a documentation-writing guide with disclosed, user-selected output integrations, though users should notice its helper command and optional Feishu/MCP account use.
This skill is coherent for writing and improving documentation. Before using non-chat outputs, especially Feishu/MCP or GitHub, confirm the destination, account, and permissions, and be comfortable with the local helper command used to detect available tools.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may run a local helper script to check whether publishing tools are available.
The skill directs the agent to run a bundled Python helper to detect output tooling. This is disclosed and aligned with output setup, but it is still local code execution.
After user selects output method, automatically check tool availability: `python3 scripts/output-handler.py --detect`
Allow the detection step only when you actually want one of the non-chat output methods, and review the helper script if you have strict local-execution requirements.
If you choose Feishu output, the skill may use an already configured Feishu/MCP account connection.
Feishu publishing may rely on local MCP/mcporter account configuration and connection testing. This is expected for Feishu output, but it involves delegated account access.
Feishu document (via MCP/mcporter) ... Check if MCP feishu server is configured ... `/root/config/mcporter.json` or `~/.mcporter/mcporter.json` ... Test connection to Feishu MCP server
Confirm the Feishu workspace/account and permissions before using this output path, and avoid selecting it for documents you do not want sent to that service.
Document content may pass through the configured MCP/Feishu integration when that output method is selected.
The optional Feishu path routes output through an MCP/mcporter integration. This is disclosed, but it introduces an external tool/server boundary for document content.
Feishu document (via MCP/mcporter) ... Test connection to Feishu MCP server
Use the Feishu option only with trusted MCP configuration and verify the intended destination before publishing.
You may need Python or Node.js/MCPorter for some features even though the registry metadata says no required binaries.
The README documents runtime dependencies for helper scripts and MCPorter, while the registry requirements list no required binaries. This is an under-declared setup detail rather than hidden behavior.
Requirements: - Python 3.8+ - Node.js 18+ (for MCPorter integration)
Treat non-chat output features as optional integrations and install/use only the tooling you trust.