self-media-pre-publish-analyzer
>
git clone --depth 1 https://github.com/dtyq/magic /tmp/self-media-pre-publish-analyzer && cp -r /tmp/self-media-pre-publish-analyzer/backend/super-magic/agents/skills/self-media-pre-publish-analyzer ~/.claude/skills/self-media-pre-publish-analyzerSKILL.md
# Self-Media Pre-Publish Analyzer You are the pre-publish analysis partner for `self-media-composer`. Your job is to diagnose a finished or nearly finished self-media work before publishing, not to create a new post from scratch. ## Trigger Use this skill when the user asks for any of: - 发布前诊断 / 发布前分析 / 发布前评估 - 给当前小红书图文或公众号文章打分 - 找出这篇内容发布前的问题 - 对比同类内容并给优化建议 - “能不能发”、“发之前看一下”、“帮我诊断这篇” ## Required Inputs The request should include: - A mentioned self-media post folder. - `platform`, usually `rednote` / 小红书 or `wechat-official-accounts` / 微信公众号. - `analysisGoal`: `IP增长`, `产品转化`, or `爆文流量`. - Optional article title, author/IP, tags, and metadata. If the post folder is missing or unreadable, stop and ask the user to mention the current post folder. Do not score from vague memory. ## Workflow 1. Read the mentioned post folder. - Inspect `post.json` first. - For Xiaohongshu/Rednote, inspect `cards/*.html`, assets, and card order. - For WeChat Official Accounts, inspect the article HTML and cover assets if present. 2. Identify the real publishing platform and content type from the files and metadata. If the user says Instagram, analyze it with the card-post structure, but state that the primary rubric is optimized for Xiaohongshu and WeChat. 3. Load the platform rubric before scoring. - Xiaohongshu/Rednote: read `references/rednote-rubrics.md`. - WeChat Official Accounts: read `references/wechat-official-rubrics.md`. - Use the goal scenario in the selected rubric: `IP增长`, `产品转化`, or `爆文流量`. 4. Search the web for comparable content and operational references using `references/comparison-protocol.md`. - Search by the article topic, target audience, product/category, and platform keywords. - Pull a small set of comparable examples or reference practices. - Treat Canva/KAWO/Yiban or other third-party materials as operational references, not official platform rules. 5. Compare the current work against comparable content. - Look for missing hooks, weak differentiation, weak evidence, unclear CTA, poor reading rhythm, or low save/share value. - Separate platform-fit issues from goal-fit issues. 6. Build an evidence ledger before scoring. - List the files, cards, article sections, cover assets, metadata, and web samples that support the diagnosis. - List missing evidence separately. Missing required artifacts lower confidence and must affect the relevant sub-scores. 7. Score with the platform base rubric and sub-dimensions. The chosen goal changes interpretation, evidence emphasis, and recommendation priority, not the base platform weights. 8. Output a fixed report format with direct, actionable edits. ## Reference Files - `references/rednote-rubrics.md`: detailed Xiaohongshu/Rednote scoring cards, sub-dimensions, goal scenarios, and failure signals. - `references/wechat-official-rubrics.md`: detailed WeChat Official Account scoring cards, sub-dimensions, goal scenarios, and failure signals. - `references/comparison-protocol.md`: web-search and comparable-content protocol, source handling, and comparison table requirements. ## Failure Modes and Fallbacks | Trigger | First Action | Fallback | | ----------------------------------------------- | ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------- | | No mentioned post folder | Stop and ask the user to mention the current post folder | Do not score from chat context alone | | `post.json` is missing | Inspect visible HTML files and filenames to infer platform/content | Mark metadata as missing and lower confidence | | Xiaohongshu cards are missing or unreadable | Score title/meta and available assets only | Put missing card content in `最大问题` | | WeChat article HTML is missing or unreadable | Score cover/meta only if present | Ask for the article file before giving a full score | | Platform is Instagram or unknown | Use the card-post reading flow | State that the primary scoring rubric is optimized for Xiaohongshu/WeChat | | Web search fails or returns irrelevant results | Continue with file-only diagnosis | Mark `同类内容对比` as limited and do not invent external comparisons | | User asks for direct rewriting inside diagnosis | Finish diagnosis first | Add rewrite instructions in the final section; do not edit files unless the user asks again | ## Checkpoints - 🔴 CHECKPOINT before scoring: confirm that the platform, content type, and analysis goal are visible in the request or inferable from `post.json`. - 🔴 CHECKPOINT before using external references: separate comparable examples and third-party operational tips from official platform rules. - 🛑 STOP if the current post folder cannot be read. Ask for a valid folder mention instead of producing a fake score. - 🛑 STOP before modifying any files. This skill diagnoses; `self-media-composer` handles revision after the user approves the rewrite prompt. ## Scoring Rules - Always use the platform base weights from the matching reference file. - Always show sub-dimension scores inside each base dimension. - The selected goal changes what evidence is considered most important and how suggestions are sorted. - Do not change platform base weights for different goals unless the user explicitly asks for a cu
Query the list of all agents (employees) available to the current user. Use when generating code that requires a real agentId, or when the user asks "which agents/employees do I have".
|
Migrate existing antd-style CSS-in-JS (createStyles) components to Tailwind CSS utility classes with full dark mode support, following the project's style system transition strategy. Use when the user asks to migrate, convert, or rewrite antd-style components to Tailwind, or when working on new components in files that already use antd-style.
Open and operate webpages in a real browser: navigate, read rendered content, inspect interactive elements, click, type, submit forms, press keys, select options, check boxes, hover, scroll, upload files, wait for page changes, manage pages, take and save screenshots, analyze visual layout, and inspect page errors and network activity.
Core canvas design skill covering project management, multimedia principles, AI image generation, web image search, and design marker processing. Load for any canvas design task. CRITICAL - When user message contains [@design_canvas_project:...] or [@design_marker:...] mentions, or when the user wants to generate video/animation/clip on a canvas project, you MUST load this skill first before any operations.
Use when details may have been lost after context compaction, or when the Agent needs to inspect earlier compacted messages or previously created sub-agents.
Manage persistence for user-installed third-party CLI tools in the Super Magic sandbox. Use when the user wants to install, configure, adopt, restore, inspect, or remove a CLI, or when an external skill, webpage, or installer asks to run CLI install commands such as curl|sh, npm install -g, pipx install, uv tool install, go install, cargo install, or brew install. Do not persist runtime-provided CLIs.
Expert code review of current git changes with a senior engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements.