From noah-content-tools
Snowflake article writing and editing skill for Medium and the Snowflake Builders Blog. Use whenever writing, editing, drafting, or revising articles for Medium, the Snowflake Builders Blog, WAF series content, Long Game series content, or any technical article related to Snowflake, data engineering architecture, or snowfort. Also trigger when the user mentions article structure, series planning, or asks for feedback on article drafts. Enforces article-specific conventions on top of the noah-voice skill, including mandatory AI detection scoring before delivery.
How this skill is triggered — by the user, by Claude, or both
Slash command
/noah-content-tools:snowflake-articleThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill enforces article-specific conventions for Noah's Medium and Snowflake Builders Blog writing. It layers on top of the foundational voice and AI detection skills.
This skill enforces article-specific conventions for Noah's Medium and Snowflake Builders Blog writing. It layers on top of the foundational voice and AI detection skills.
Both of these skills must be loaded and applied:
references/voice-rules.md and at least one example article before writing. All voice rules apply.noah-voice skill's voice rules and at least one reference articlereferences/article-conventions.md in this skill's directory for series context, structure patterns, and technical conventionsEvery article follows this progression. Read references/article-conventions.md for detailed explanation and examples of each stage:
Start with a personal story, observation, or honest admission. Not a topic introduction. Not "In this article, we'll explore..." The reader should feel something before they learn something. Noah's Databricks article opens with admitting his previous article was wrong. The Long Game opens with reflecting on the Data Superhero title.
Introduce the central metaphor that will carry the entire piece. This is the teaching tool. The metaphor must be:
Refer to the PoEAA/Rails pattern in references/article-conventions.md: hook with the metaphor, unpack as an analogy, apply to the technical problem.
Deliver the substance through the lens of the metaphor. This is where code blocks, architectural patterns, and Snowflake-specific content lives.
Code formatting rules:
This is the ONE place bullet points are acceptable. Keep it to 3-5 actionable items. Link to resources, next articles in the series, or community connections.
When writing for either series, maintain awareness of how they connect:
The Long Game = philosophical foundation (leadership, stewardship, mentoring)
WAF Series = practical manual (architecture, implementation, snowfort)
Connection: The CCC mental model (Calm, Connect, Coach) bridges both. See references/article-conventions.md for details.
When referencing the other series, do it naturally: "As I explored in The Long Game, the real test of architecture isn't how it performs under your watch..." Don't force cross-references. Let them emerge from the content.
Before presenting any article draft:
ai-scoring skillIf the article is close (70-74), note the specific flags and let Noah decide whether to revise or accept.
This analysis is available on request only, not automatic. When Noah asks for it, follow the process described in references/article-conventions.md: map every major point, count repetitions, distinguish intentional reinforcement from accidental redundancy, and propose a tighter structure.
Watch out for these patterns that are especially common when writing about data platforms:
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub noah-goodrich/claude-plugins --plugin noah-content-tools