Skip to content
TrustedSkillsbeta
Back to all skills

Blog Audit

Checked
agricidaniel·vlatest·writing·MIT

Analyze existing blog content for SEO, readability, and engagement opportunities with data-driven recommendations.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add agricidaniel/claude-blog --skill blog-audit -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

agricidaniel

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned agricidaniel/claude-blog at 2500d4c765.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
2500d4c765
Manifest
skills/blog-audit/SKILL.md
Scanned
1 file, 241 lines
Copies in repo
2 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The blog-audit skill analyzes a given blog post URL and provides feedback on its SEO performance. It identifies potential issues like missing meta descriptions, broken links, or keyword density problems. The tool aims to help improve the visibility and ranking of blog content in search engine results.

When to use it

  • You want to quickly assess the SEO health of a newly published blog post before promotion.
  • You're trying to understand why an existing blog post isn’t performing well in search results.
  • You need a regular check-up for your blog content to ensure ongoing optimization.
  • You are looking for suggestions on how to improve the technical SEO of a specific article.

Key capabilities

  • Analyzes blog posts from provided URLs.
  • Identifies potential SEO issues.
  • Provides feedback and suggestions for improvement.

Example prompts

  • "Audit this blog post: [blog post URL]"
  • "Can you analyze the SEO of [blog post URL]?"
  • “Give me an audit report for my article at [blog post URL].”

Tips & gotchas

The skill requires a valid, publicly accessible URL to perform its analysis. Results should be interpreted as suggestions; always use your own judgment and expertise when implementing changes.