Loading...
Loading...
Found 48 Skills
Multi-perspective adversarial review. 4 Agents are spawned in parallel (full mode), each identifying issues from different perspectives, and the main thread makes a comprehensive ruling. Trigger methods: /story-review, /审查, "审查一下", "帮我审一下"
Sales content management — organizing, distributing, and measuring sales collateral (battle cards, one-pagers, case studies, decks, playbooks, ROI calculators). Also covers content governance, content audits, and sales-marketing alignment on content. Use when building a content library, creating battle cards, organizing sales collateral, auditing content usage, improving content findability, aligning marketing and sales on content needs, or measuring content effectiveness. Do NOT use for writing marketing copy (use /copywriting), Seismic-specific platform help (use /sales-seismic), proposal page design (use /sales-proposal-page), or email sequence copywriting (use /sales-cadence).
Reviews documentation PRs and provides GitHub PR suggestions. Load when asked to review, suggest changes, or provide feedback on docs content. Covers MDX, frontmatter, style guide, components, and content accuracy.
Run a comprehensive Go-to-Market and launch readiness review for a project phase. Combines marketing content audit, code quality review, performance audit, accessibility audit, infrastructure readiness, and business review with council evaluation. Use before phase launches or when GTM review issues are ready.
Review content against your brand voice, style guide, and messaging pillars, flagging deviations by severity with specific before/after fixes. Use when checking a draft before it ships, when auditing copy for voice consistency and terminology, or when screening for unsubstantiated claims, missing disclaimers, and other legal flags.
Systematically review biblical content through a 10-point quality checklist. Works with bible-buddy reference files, any file path, URLs, or text pasted directly in the conversation. Use when asked to review, audit, check, or verify biblical content. Trigger on: "檢查冷知識", "fact check", "檢查經文", "review bible", "幫我檢查這段", "bible-fact-check", or any request to find errors, duplicates, or issues in biblical reference content.
Define what content a product needs, how it should be structured, and who owns it.
This skill orchestrates autonomous discovery of brand materials across enterprise platforms (Notion, Confluence, Google Drive, Box, SharePoint, Figma, Gong, Granola, Slack). It should be used when the user asks to "discover brand materials", "find brand documents", "search for brand guidelines", "audit brand content", "what brand materials do we have", "find our style guide", "where are our brand docs", "do we have a style guide", "discover brand voice", "brand content audit", or "find brand assets".
Novel Logic/Plot Review, applicable to user requests such as "Help me check if there are bugs in my novel", "Check if there are timeline contradictions", "Check if characters are OOC", "Find plot conflicts between different parts", "Sort out whether foreshadowings are resolved", "Check the rationality of novel plots", "Check if there are plot loopholes", "Character behaviors are inconsistent with their personalities", "Check if the timeline is correct", "Find contradictions in the novel", "Help me sort out all foreshadowings", "Novel plot bug check", "Logical loophole troubleshooting", etc. It detects issues such as timeline conflicts, logical loopholes, character OOC, and missing foreshadowings. **Performs word count checks to ensure chapter word counts meet standards**, **generates a detailed issue list and automatically fixes all issues, with the fixed results directly modifying the chapters/ directory and automatically backing up the original files to .sumeru/write/original/ before modification**, **uses sub-Agents for parallel processing during batch review, with each Agent responsible for a maximum of 3 chapters**
Review content files against a project's voice and style guidelines. Use when reviewing written content (MDX, markdown, copy) for tone, sentence structure, word choice, and bilingual policy compliance before committing. Triggers on "review voice", "check tone", "voice review", "content review", "does this match our voice", or after writing loop/ritual/article content.
Detect and flag AI-generated content markers in documentation and prose. Use when reviewing documentation for AI markers, cleaning up LLM-generated content, or auditing prose quality. Do not use when generating new content (use doc-generator) or learning writing styles (use style-learner).
Apply cognitive fluency principles to improve clarity, trust, and conversion. Use when designing landing pages, writing copy, creating interfaces, or optimizing any content for better user comprehension and engagement.