agentleFS
RightBloggerRightBlogger/bloggingskills/skills/house-style/SKILL.md

house-style

Skill4 starsChanged 15 days agoMITView on GitHub

Audits a draft against the collection's writing rulebook of AI tells without rewriting it, and records a blog's own style variations. The rulebook is the shared standard every writing skill reads. Use when the user says 'house style', 'style guide', 'does this follow our style', 'audit this draft', or 'set our writing rules'. For rewriting an AI-sounding draft, see humanize. For niche, audience, and voice setup, see blog-context.

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every writing skill in this collection reads this rulebook before it drafts or edits.

    line 12

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

House style

You own the writing standard for this blog: the rules that keep every post readable, human, and consistent no matter which skill or which day produced it. Every writing skill in this collection reads this rulebook before it drafts or edits.

You're done when an audit lists every hard-rule hit and every repeating tell with a fix, or when the user's own variations are recorded where every skill reads them.

The rulebook

The full standard lives in references/ai-tells.md. Read it before anything else. It has two tiers: hard rules that apply to every line written (no em dashes, no fabricated claims, no chatbot residue), and frequency tells that only count when they repeat or stack.

Precedence, highest first: the user's explicit request, then a captured voice in .agents/blog-context.md or a brand-voice profile, then the rulebook. If following the rulebook would break something the user asked for, do what the user asked and mention the conflict in one line.

What this skill does

  1. Audit. Handed a draft, report against the rulebook without rewriting it. List every hard-rule hit, then the frequency tells that repeat, each with the offending quote and a fix. Lead with whatever does the most damage.
  2. Customize. When the user wants their own variations (British spelling, an Oxford comma policy, jargon allowed for an expert audience, brand-banned words), record them under "House-style deltas" in the Voice section of .agents/blog-context.md so every skill inherits them. Don't edit the rulebook itself for one blog's preferences.

Output (audit mode)

  • A one-line verdict: does this read human, and the top three reasons.
  • A table of violations: tier, pattern, offending quote, fix. Hard-rule hits first.
  • A count of the worst repeat offenders (em dashes: 14, "it's not X": 6).
  • A pointer to humanize for the rewrite. The audit itself doesn't rewrite.

Related skills

humanize · brand-voice · article · blog-context · seo-optimize

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.