Content Writer Agent
mastra-ai/mastra
Authoring playbook for building agents that draft written content — blog posts, marketing copy, social media posts, newsletters, product descriptions, landing pages, or ad copy.
A skill your agent uses when evaluating content pages for SEO quality.
Install Quality
$ npx skills add thedaviddias/Front-End-Checklist --skill quality -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/Front-End-Checklist quality --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/quality .claude/skills/quality && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "quality" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/quality into .claude/skills/quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quality", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/qualityType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add thedaviddias/Front-End-Checklist --skill quality -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/Front-End-Checklist quality --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/quality .agents/skills/quality && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "quality" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/quality into .agents/skills/quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quality", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill quality -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/Front-End-Checklist quality --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/quality .cursor/skills/quality && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "quality" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/quality into .cursor/skills/quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quality", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/thedaviddias/Front-End-Checklist.git --path skills/quality--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add thedaviddias/Front-End-Checklist --skill quality -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/Front-End-Checklist quality --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/quality .gemini/skills/quality && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "quality" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/quality into .gemini/skills/quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quality", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install thedaviddias/Front-End-Checklist qualityInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add thedaviddias/Front-End-Checklist --skill quality -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/quality .github/skills/quality && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "quality" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/quality into .github/skills/quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quality", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill quality -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install thedaviddias/Front-End-Checklist quality --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/quality .opencode/skills/quality && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "quality" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/quality into .opencode/skills/quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quality", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
quality- GitHub stars
- 74k
- Token cost
- ~654 tokens
- SKILL.md length
- 301 words
- Files
- 2 (incl. references)
- Skills in repo
- 390
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when evaluating content pages for SEO quality.
- Evaluating content pages for SEO quality
- SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Landing pages
What it does
Quality is an agent skill from thedaviddias/Front-End-Checklist. Use when evaluating content pages for SEO quality. Applies to blog posts, product descriptions, landing pages, or any page expected to receive organic search traffic.
Its SKILL.md is about 650 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/rule.md`).
It sits in Writing & Content, covering Landing pages, Copywriting and Blog and article writing. The repository describes itself as: 🗂 The essential checklist for modern web development, for humans and AI agents. The licence is MIT.
When your agent uses it
- Evaluating content pages for SEO quality
- Tasks that involve Landing pages
- Tasks that involve Copywriting
Example prompts
- “/quality”
What it can do on your machine
Read from SKILL.md and the folder at commit e8d14d0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
frontendchecklist.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Quality loads about 654 tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 44 tokens; SKILL.md has 301 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 301 words, ~654 tokens.
Download SKILL.mdSave it as
.claude/skills/quality/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- quality
- description
- Use when evaluating content pages for SEO quality. Applies to blog posts, product descriptions, landing pages, or any page expected to receive organic search traffic.
- metadata.category
- seo
- metadata.priority
- high
- metadata.difficulty
- intermediate
- metadata.estimatedTime
- 30
- metadata.source
- frontendchecklist.io
- metadata.url
- https://frontendchecklist.io/rules/seo/quality
Publish high-quality content
Google's Search Quality Rater Guidelines and Helpful Content system reward pages that demonstrate genuine expertise and fully satisfy user intent—low-quality pages are algorithmically suppressed site-wide.
Quick Reference
- Content quality is Google's primary ranking differentiator—E-E-A-T applies to every page
- Thin content (low word count, generic text) is a leading cause of ranking loss
- Each page must have a clear primary purpose and fully satisfy user intent
- First-hand experience, expert authorship, and cited sources raise quality signals
Check
Evaluate this page's content for E-E-A-T signals: Does it demonstrate first-hand experience or expertise? Does it fully answer the apparent search intent? Is the information accurate, specific, and supported by evidence? Is there meaningful depth beyond what competitors cover? Identify specific quality gaps.
Fix
Identify the primary search intent for this page. Rewrite or expand the content to: (1) fully satisfy that intent, (2) add specific details, examples, or data not found on competing pages, (3) attribute claims to authoritative sources, (4) add author byline with relevant credentials, (5) update any outdated information.
Explain
Google's ranking systems are designed to surface content that demonstrates Experience, Expertise, Authoritativeness, and Trustworthiness (E-E-A-T). Content that is generic, lacks depth, or does not fully answer user questions is classified as 'unhelpful' and deprioritised in rankings. High-quality content is the most durable long-term SEO investment.
Code Review
Analyse the page content for quality signals: (1) Word count — is the topic covered in appropriate depth? (2) Specificity — are claims backed by data or examples? (3) Authorship — is a named author with credentials visible? (4) Freshness — does the page show a publication or updated date? (5) Sources — are external authoritative sources cited? (6) Originality — does the content offer unique insights not found on competing pages?
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
© thedaviddias, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/quality of thedaviddias/Front-End-Checklist.
- SKILL.md
- references/rule.md
Open the folder on GitHubat commit e8d14d0
Compare with similar skills
Quality next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Quality this skillthedaviddias/Front-End-Checklist | 74k | — | ~654 | Automated safety check: Pass | MIT | |
| Content Writer Agentmastra-ai/mastra | 29k | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| No Em Dashespetera2c/simple-table | 229 | — | ~195 | Automated safety check: Pass | MIT | |
| Money Contentiamzifei/show-me-the-money | 1k | — | ~9.6k | Automated safety check: Pass | Custom licence | |
| Content Engineindranilbanerjee/digital-marketing-pro | 859 | 1 repos | ~8.9k | Automated safety check: Pass | MIT | |
| Mkt Content Creationevolution-foundation/evo-nexus | 545 | — | ~2.2k | Automated safety check: Pass | Custom licence |
Similar skills
No Em Dashes
petera2c/simple-table
Avoid em dashes in marketing copy, hero text, changelogs, blog posts, docs, UI strings, and chat.
Money Content
iamzifei/show-me-the-money
Automated content creation pipeline for business growth. An agent skill from iamzifei/show-me-the-money.
Content Engine
indranilbanerjee/digital-marketing-pro
Draft marketing content in brand voice — blog posts, ad copy, email sequences, social posts, landing pages, and brand-voice guides — through a gated pipeline (research, outline, draft, fact-check…
Mkt Content Creation
evolution-foundation/evo-nexus
Draft marketing content across channels — blog posts, social media, email newsletters, landing pages, press releases, and case studies.
Copywriting
freekmurze/dotfiles
When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages.
More from thedaviddias/Front-End-Checklist
All 390 skills in this repoContent Dates Audit
thedaviddias/Front-End-Checklist
Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.
FAQPage Schema Markup
thedaviddias/Front-End-Checklist
Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.
Favicon Audit and Setup
thedaviddias/Front-End-Checklist
Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.
Content Freshness Signals
thedaviddias/Front-End-Checklist
Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.
Geo Meta Tags Audit
thedaviddias/Front-End-Checklist
Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).
Improve a Front-End Checklist Rule
thedaviddias/Front-End-Checklist
Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.
Related
Categories
Questions about Quality
What does Quality do?
A skill your agent uses when evaluating content pages for SEO quality. Quality is an agent skill from thedaviddias/Front-End-Checklist. Use when evaluating content pages for SEO quality.
When should I use Quality?
Quality fits situations like: evaluating content pages for SEO quality; tasks that involve Landing pages; tasks that involve Copywriting.
How do I install Quality in Claude Code?
Run `npx skills add thedaviddias/Front-End-Checklist --skill quality -a claude-code`. Or copy the skill folder (skills/quality in thedaviddias/Front-End-Checklist) into .claude/skills/quality in your project. Claude Code loads it when a task matches its description.
How do I install Quality in Codex?
Run `npx skills add thedaviddias/Front-End-Checklist --skill quality -a codex`. Or copy the skill folder (skills/quality in thedaviddias/Front-End-Checklist) into .agents/skills/quality in your project. Codex loads it when a task matches its description.
Can I use Quality in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thedaviddias/Front-End-Checklist --skill quality -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/quality, .gemini/skills/quality, .github/skills/quality and .opencode/skills/quality in your project.
What does Quality need to run?
SKILL.md names no scripts, command-line tools or credentials: Quality is instructions for the agent only.
Does Quality access the network?
SKILL.md names 1 domain. As links in the text: frontendchecklist.io. This is read from the text; nothing was executed.
Is Quality safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Quality use?
Quality is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Quality use?
About 654 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.
What are the alternatives to Quality?
Skills that share tags, products or a category with Quality: Content Writer Agent (mastra-ai/mastra, 29k stars), No Em Dashes (petera2c/simple-table, 229 stars), Money Content (iamzifei/show-me-the-money, 1k stars) and Content Engine (indranilbanerjee/digital-marketing-pro, 859 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Quality?
thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,412 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.
Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.