SKILLEMALL.ai

AB chatpipe-export

Export any AI chat session to Markdown, JSON, or plain text using ChatPipe v1.1. Supports 7 input formats including OpenClaw sessions, Hermes agent logs, ChatGPT exports, and Chatbox exports. Use when the user asks to export/backup their chat history, convert conversations to Obsidian/Notion, or migrate between AI platforms. Free skill wraps the open-source ChatPipe engine. Triggers: "导出聊天记录", "export chat", "save conversation", "backup my chats", "导出到Obsidian", "导出到Notion", "convert to markdown", "chat export".

ClawHub Agent Skills author: hanyuanchen08-netizen v1.0.1 MIT-0 3 files · 1 script body ≈ 519 tokens Open the sourceclawhub.ai↗ analyzed 7 d ago

Export any AI chat session to Markdown, JSON, or plain text using ChatPipe v1.1. Supports 7 input formats including OpenClaw sessions, Hermes agent logs…

As a process B 67/100 · Nearly there — weak spots: failures and branches

GeneratorObsidianNotionAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
98/100
safety, quality, tests
Safety 60%
100
Quality 40%
95
Run on models
none yet
Process rating
B
67/100
Nearly there
Failures and branches w 10
0
Tools and files w 18
60
Result and completion w 14
60
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 67/100

    • 0Failures and branches. Linear process with no failure handling
    • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 75Steps. 3 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 519 tokens
    • 100Running it twice. No mutating operations
    • 100Progress reporting. Reports progress

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +4Description does not say when NOT to use the skill (false activations)
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 8 example trigger phrases
    • +3Description length 517: enough signal without eating the budget
    • +4Structure: 8 headings
    • +3Step-by-step instructions: 3 items
    • +3Output format is stated explicitly
    • +4Has examples (3 code blocks)
    • +3All 1 scripts are documented

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 95.

    External checks

    ClawHub: suspicious
    The skill has a legitimate chat-export purpose, but it can persist sensitive chat transcripts with broad activation and incomplete scoping or warnings.
    LLM: suspicious (high) · 26 Jul 2026