doc-spellcheckDetect and automatically fix spelling errors in Markdown, plain text, and documentation files with support for custom dictionaries and batch processing.
Install via ClawdBot CLI:
clawdbot install linux2010/doc-spellcheckGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://github.com/Linux2010/openclaw-skillsAudited Apr 17, 2026 · audit v1.0
Generated Mar 20, 2026
Maintainers of open source projects can use this skill to ensure all documentation files (READMEs, guides, API docs) are free from spelling errors before releases. It helps maintain professional quality across community contributions and reduces manual proofreading time.
Technical writing teams can integrate this skill into their documentation workflow to enforce consistent spelling and terminology across all documentation assets. The custom dictionary feature ensures domain-specific terms are correctly recognized while common errors are automatically fixed.
Educational platforms and course creators can use this skill to proofread lesson materials, tutorials, and educational content in Markdown format. The batch processing capability allows checking entire course directories efficiently before publication.
Large organizations can implement this skill in their CI/CD pipelines to enforce documentation quality standards across all teams. The JSON output format integrates with existing monitoring systems, and Git integration ensures clean audit trails for documentation changes.
CMS platforms can integrate this skill as a pre-publish check for content editors working with Markdown content. The interactive correction mode allows editors to review suggestions before publishing, improving content quality with minimal disruption to workflow.
Offer basic spell checking as a free service with limited monthly checks, then charge for advanced features like custom dictionaries, batch processing, CI/CD integration, and priority support. Target documentation-heavy companies with tiered pricing based on usage volume.
Sell annual enterprise licenses to large organizations needing documentation quality assurance across multiple teams. Include features like on-premise deployment, custom language packs, dedicated support, and integration with existing documentation platforms.
License the technology to IDE and code editor companies (VS Code, JetBrains, etc.) to include as a built-in documentation quality feature. Charge per-user licensing fees or revenue sharing agreements based on user adoption within their platforms.
💬 Integration Tip
Start by adding the spell check as a pre-commit hook in your Git workflow to catch errors early, then gradually expand to CI/CD pipelines for automated quality gates across all documentation changes.
Scored Apr 19, 2026
Manage a personal knowledge base by adding, searching, organizing, and reviewing articles, links, and notes with tags and natural language queries.
Generate a daily work report by automatically discovering all git repositories the user worked on, collecting commit logs across all branches, and summarizin...
日记引导助手。每日写作引导、感恩日记、反思日记、晨间日记、晚间总结、周总结模板。Journal prompts for daily writing, gratitude, reflection, morning pages, evening review, weekly summary. 日记、写作、反思、感恩。
Use when maintaining RDR2 (Red Dead Redemption 2) playthrough notes — logging an acquisition ("acquired X", "got N gold bars", "finished X"), answering in-game location/crafting questions, or reviewing the notes for duplicate or stale info. Triggers on RDR2, Red Dead Redemption, playthrough, legendary animal, talisman, trinket, valerian root, gold bar, horse, weapon, berry.
Use when a sales rep already has a customer who has expressed some need (from outreach follow-up, account-landing research, customer-initiated contact, or meeting notes) and needs to structurally validate whether that need is real, urgent, whose pain it actually is, and whether it matches the team's capability — before pushing to ROI proofing or buying-intent assessment. Triggers: '验证一下这个需求是不是真的', '需求真不真', '客户说痛但我不确定', '这个客户值不值得跟', '客户说会考虑但是真的吗', '谁拍板', '现有方案是什么', '切换成本', 'need validation', 'pain point validation', 'is this a real need', 'verify customer need'. Do NOT use for: scoring leads at line-item level, building target-customer profiles, calculating ROI, overall buying-intent scoring, opportunity-stage assessment, or writing outreach/cold messages.
Microsoft OneNote integration. Manage Notebooks. Use when the user wants to interact with Microsoft OneNote data.