wt-writing-auditor

Audit Liam Bastick-style blog articles against UK English and custom house rules.

1|Updated Jun 12, 2026
One-click install
npx skills add https://github.com/Sampi314/Sam-Plugin-Marketplace --skill wt-writing-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wt-writing-auditor
Source: https://github.com/Sampi314/Sam-Plugin-Marketplace/tree/main/Writing%20Tools/skills/wt-writing-auditor
Command: npx skills add https://github.com/Sampi314/Sam-Plugin-Marketplace --skill wt-writing-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manually reviewing Liam Bastick-style blog articles (DAX, Excel, Final Friday Fix, Monday Morning Mulling, AI blog) against his specific editorial standards is time-consuming and prone to missing nuanced rules around UK English, formatting, technical accuracy, and series-specific conventions. This Skill automates the full audit workflow, eliminating manual review effort and ensuring consistent compliance with Liam's quality gate.

Core Features & Use Cases

  • Two-Tier Rule Auditing: Checks content against both standard UK English rules and Liam Bastick's custom editorial house rules, covering grammar, formatting, technical accuracy, tone, product name spacing, and series-specific template compliance.
  • Stale Fact Web Verification: Automatically verifies technical claims (DAX function syntax, Power Pivot compatibility, AI tool features, Excel function availability) against current online sources to catch outdated content that static rule checks miss.
  • Dual Output Generation: Produces a markdown error report grouped by severity (Critical / Major / Minor / Suggestion) with rule references, plus a tracked-changes Word document that preserves the original document's formatting, images, and styles for Liam to review and accept/reject changes individually.
  • Use Case: A SumProduct content editor can use this Skill to audit a new DAX A-to-Z article before publication, catching technical errors like incorrect Power Pivot compatibility claims, formatting mistakes like un-bolded function names, and UK English errors like American spellings in seconds.

Quick Start

Use the wt-writing-auditor skill to audit the attached Liam-style article 'LEN Function.docx' against Liam's editorial standards and generate a tracked-changes Word document with all approved fixes applied.

Frequently Asked Questions about wt-writing-auditor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a blog article against UK English and custom editorial house rules?

To audit a blog article against UK English and custom editorial house rules, this Skill checks content against a two-tier system of standard UK English and Liam Bastick's custom house rules, identifying grammar, formatting, technical accuracy, and tone errors automatically.

Can I generate a tracked-changes Word document that preserves my original formatting when editing an article?

Yes, you can generate a tracked-changes Word document that preserves original document formatting, images, and styles. This allows reviewers to accept or reject individual edits made during the editorial audit process directly within the document.

How do I verify stale technical facts in DAX and Excel articles before publishing?

To verify stale technical facts in DAX and Excel articles, this Skill performs mandatory web verification of DAX function syntax, Power Pivot compatibility, AI tool currency, and Excel function availability against current online sources to catch outdated content.

What is the best way to check SumProduct content series for editorial compliance?

The best way to check SumProduct content series for editorial compliance is using this automated audit workflow, which applies Liam Bastick's quality gate to DAX A-to-Z, Excel A-to-Z, Final Friday Fix, Monday Morning Mulling, and AI blog posts to ensure consistent standards.

Does the editorial audit report group errors by severity?

Yes, the editorial audit report groups identified errors by severity into Critical, Major, Minor, and Suggestion categories. This markdown report includes rule references so editors can prioritize fixes based on the severity of the editorial or technical issue.