Skip to content
TrustedSkillsbeta
Back to all skills

Blog Analyze

Checked
agricidaniel·vlatest·writing·MIT

Analyzes blog posts for readability, SEO keywords, audience sentiment, and content improvement suggestions.

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-analyze -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.

Scanned
1 file, 330 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-analyze skill analyzes blog posts to extract key information. It can identify topics, sentiment, and potential areas for improvement in writing style or clarity. This allows users to quickly understand the essence of a blog post without needing to read the entire article.

When to use it

  • Content Research: Quickly assess the core themes and arguments presented in multiple blog posts related to a specific topic.
  • Competitive Analysis: Evaluate competitor blogs by analyzing their content's tone, topics, and writing style.
  • Blog Improvement: Get feedback on your own blog posts regarding clarity, sentiment, and potential areas for refinement.
  • Summarization: Quickly understand the main points of a lengthy or complex blog post.

Key capabilities

  • Topic identification
  • Sentiment analysis
  • Writing style assessment

Example prompts

  • "Analyze this blog post: [URL]"
  • "What are the key topics discussed in this article? [URL]"
  • "Assess the sentiment of this blog post and suggest improvements to its writing. [URL]"

Tips & gotchas

The skill's effectiveness depends on the quality and clarity of the input blog post. Very short or poorly written posts may yield less accurate results.