Creator · AgriciDaniel
Last updated · Sep 2, 2026
Full-site blog health assessment scanning all blog files for quality scores, orphan pages, topic cannibalization, stale content, and AI citation readiness. Runs canonical batch analysis before site-wide checks. Produces per-post scores and a prioritized action queue. Use when use
Creator · AgriciDaniel
Last updated · Sep 2, 2026
Full-site blog health assessment scanning all blog files for quality scores, orphan pages, topic cannibalization, stale content, and AI citation readiness. Runs canonical batch analysis before site-wide checks. Produces per-post scores and a prioritized action queue. Use when use
Creator · AgriciDaniel
Last updated · Sep 2, 2026
Full-site blog health assessment scanning all blog files for quality scores, orphan pages, topic cannibalization, stale content, and AI citation readiness. Runs canonical batch analysis before site-wide checks. Produces per-post scores and a prioritized action queue. Use when use
Creator · AgriciDaniel
Last updated · Sep 2, 2026
Full-site blog health assessment scanning all blog files for quality scores, orphan pages, topic cannibalization, stale content, and AI citation readiness. Runs canonical batch analysis before site-wide checks. Produces per-post scores and a prioritized action queue. Use when use
Sandbox only
Install targets
Codex install prompt
Install the "blog-audit" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/brain/.raw/sources/claude-blog-skill/skills/blog-audit. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Full-site blog health assessment scanning all blog files for quality scores, orphan pages, topic cannibalization, stale content, and AI citation readiness. Runs canonical batch analysis before site-wide checks. Produces per-post scores and a prioritized action queue. Use when user says "audit blog", "blog audit", "site audit", "blog health", "audit all posts", "check all blogs". After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"agricidaniel-blog-audit","task":"Install blog-audit","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
Research agents
I need my agent to research a topic, compare sources, and produce a concise report.
Agent fit
Claude Code + OpenAI Agents + CLI
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add AgriciDaniel/claude-blog --skill blog-audit
Maintenance
fresh
8d since push
Risk
Needs review
Dependency or permission surface needs review
GitHub quality
2.0K
80/100 Quality · 77/100 Trust
Coverage tags
Review notes
Dependency or permission surface needs review · Permission surface may require sandboxing
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
StrongSolid option that is likely worth shortlisting for production workflows.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
2.0K GitHub stars
Repo activity
2.0K stars, 333 forks
Maintenance
8d since push
License
MIT
Install
npx skills add AgriciDaniel/claude-blog --skill blog-audit
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add AgriciDaniel/claude-blog --skill blog-auditDo not use when
Agent safety v2
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
Test manually in an isolated workspace and compare against safer alternatives.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
high
Skill metadata references credentials, tokens, environment variables, or secret-bearing workflows.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20blog-audit%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20blog-audit%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/agricidaniel-blog-audit/install
Agent should check
Copy prompt
Task: Use blog-audit in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20blog-audit%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/agricidaniel-blog-audit/install
Install command: npx skills add AgriciDaniel/claude-blog --skill blog-audit
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/agricidaniel-blog-audit/install
LLM text format
/api/skills/agricidaniel-blog-audit/install?format=text
Find alternatives
/api/skills/search?q=blog-audit&limit=3
Agent prompt
Use blog-audit for this task. Review https://www.openagentskill.com/api/skills/agricidaniel-blog-audit/install, then install with: npx skills add AgriciDaniel/claude-blog --skill blog-auditRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/agricidaniel-blog-audit
LLM text
/api/registry/manifest/agricidaniel-blog-audit?format=text
Install alias
/api/registry/install/agricidaniel-blog-audit
Recommend
/api/registry/recommend?task=Use%20blog-audit%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Use-case tags
Platforms
Claude Code, OpenAI Agents
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Role in stack
Primary pick
Primary fit
Research agents
Trust label
Production-ready
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
PASS2.0K GitHub stars
Stars/forks activity
PASS2.0K stars, 333 forks; issue activity unavailable in current metadata
Recent maintenance
PASS8d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Solid option that is likely worth shortlisting for production workflows.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Manage repositories
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Publish consistently
I need my agent to turn research and product updates into useful content drafts.
Workflow fit
Scrape, clean, and reuse web data
A practical workflow for agents that crawl public pages, extract clean content, normalize data, and hand it to downstream research or RAG workflows.
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Ingest, retrieve, and cite
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Alternative shortlist
Similar skills that may fit this task.
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
🕵️♂️ Collect a dossier on a person by username from 3000+ sites
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
Infisical is the open-source platform for secrets, certificates, and privileged access management.
--- name: blog-audit description: > Full-site blog health assessment scanning all blog files for quality scores, orphan pages, topic cannibalization, stale content, and AI citation readiness. Runs canonical batch analysis before site-wide checks. Produces per-post scores and a prioritized action queue. Use when user says "audit blog", "blog audit", "site audit", "blog health", "audit all posts", "check all blogs". user-invokable: true argument-hint: "[directory]" license: MIT ---
# Blog Audit: Full-Site Health Assessment
Performs a comprehensive blog health assessment across all posts in the project. Scans for quality scores, orphan pages, topic cannibalization, stale content, and AI citation readiness. Uses the canonical analyzer JSON as the score source and produces a prioritized action queue.
## Audit Process
### Step 1: Discover Blog Files
Scan the project for all blog content files:
- Recursively glob for `.md`, `.mdx`, `.html`, `.astro`, `.svelte`, `.vue`, `.tsx`, and `.jsx` in common blog directories and CMS export folders - Common paths to check: - `content/` - `posts/` - `blog/` - `src/content/` - `_posts/` - `pages/blog/` - `articles/` - `content/blog/**` - CMS export folders explicitly provided by the user - `src/pages/blog/` - Filter out hidden, vendor, generated, and secret-adjacent paths: `.git/`, dot-directories, `node_modules/`, `vendor/`, `dist/`, `build/`, `.next/`, `coverage/`, `reports/`, generated exports, README, CHANGELOG, LICENSE, config files, SKILL.md, package files, `.env*`, keys, and private notes - Report: "Found N blog files in [directories]"
If no blog files are found in standard locations, ask for an allow-listed root or only search user-approved content directories. Do not scan the entire project root by default.
### Step 2: Canonical Batch Analysis
Run canonical analyzer output first and use it as the source of per-post scores:
```bash python3 scripts/analyze_blog.py <blog-root> --batch --format json ```
Process files in chunks, cap parallel follow-up work to a small fixed number, respect context limits, and aggregate deterministic JSON with `file`, `score`, `categories`, `issues`, and `metadata`. Layer the site-wide checks below on top of analyzer JSON, not separate scoring rubrics.
#### Content Quality Layer - Score each post on the 30-point content quality scale - Check paragraph length (target 40-80 words, hard limit 150) - Check sentence length (target 15-20 words) - Evaluate heading structure and question-format headings - Assess readability using persona and content type: consumer content favors easier bands, professional content can be moderate, and technical content may be denser when clarity remains high
#### SEO Optimization Layer - Check on-page SEO elements per post: - Title tag length (40-60 acceptable, 50-60 ideal, preview warning only) - Meta description is concise and page-specific. Statistics are optional and must be visible and sourced - H1 presence and uniqueness - Image alt text coverage - Internal and external link counts - URL slug quality
#### Schema Validation Layer - Detect structured data across all posts - Validate Article/BlogPosting, Person, Organization, and BreadcrumbList schema completeness - If FAQPage exists, validate it as optional entity markup only, not a Google rich result - Normalize `dateModified`, `lastUpdated`, `updated`, and `lastmod`, including timezone-normalized generated schema, then require freshness parity - Flag missing or malformed schema
#### Link Health Layer - Map internal links across all posts - Build a directed link graph - Detect orphan pages (zero inbound internal links) - Detect dead-end pages (zero outbound internal links) - Check for broken internal link targets - Recommend bidirectional link opportunities
#### Freshness Check Layer - Read lastUpdated or dateModified from each post's frontmatter - Calculate days since last update - Flag freshness by content type, source or statistic age, and GSC decay, not by a universal day count - Categorize by refresh priority
#### AI Readiness Layer - Score each post for AI citation readiness - Check passage-level citability (120-180 word sections) - Evaluate Q&A formatting and entity clarity - Check for TL;DR boxes and citation capsules - Check robots.txt, llms.txt, SSR/SSG output, JS-gated content, blocked assets, GPTBot, ClaudeBot, PerplexityBot, Googlebot, and Google-Extended policies
### Step 2.5: Technical Crawl and Search Performance
Add site-wide technical checks before final recommendations:
- Validate sitemap coverage, robots.txt, noindex directives, canonical tags, redirects, HTTP status codes, hreflang, and internal canonical consistency - Use `blog-google` when available for Core Web Vitals, GSC queries, URL Inspection, indexing status, and GA4 context - Report skipped optional checks with reasons such as `SKIPPED: credentials unavailable`
### Step 3: Topic Cannibalization Detection
Analyze across all posts for keyword competition:
1. Extract primary keyword/topic from each post: - Title text - H1 heading - Meta description - First paragraph 2. Normalize keywords with stopword handling, lemmatization, locale awareness, and intent modifiers 3. Cluster by intent using analyzer data, embeddings or explicit confidence, GSC query-to-URL data when available, and SERP overlap where available 4. Flag competing posts with one of these recommendations: - **Merge**: Combine two weak posts into one strong post - **Redirect**: 301 redirect the weaker post to the stronger one after preserving backlinks, validating a redirect map, and updating internal links - **Differentiate**: Adjust focus so posts target distinct intents
### Step 4: Orphan Page Detection
Build and analyze the internal link graph:
1. Normalize URLs against site config and sitemap, including relative links, same-domain absolutes, trailing slashes, generated routes, anchors, and slug mappings 2. Build an adjacency map: `{ page -> [pages it links to] }` 3. Build a reverse map: `{ page -> [pages linking to it] }` 4. Identify orphan pages: posts with zero inbound internal links 5. Identify dead-end pages: posts with zero outbound internal links 6. For each orphan, recommend 2-3 existing posts that should link to it based on topic relevance
### Step 5: Stale Content Detection
Audit content freshness across all posts:
1. Read frontmatter fields: `lastUpdated`, `dateModified`, `date`, `updated` 2. Calculate days since last update for each post 3. Categorize by refresh priority: - **High**: Volatile topic, stale sources or statistics, or GSC decay - **Medium**: Evergreen topic with aging examples, links, or screenshots - **Low**: Recently validated or stable reference content 4. Estimate refresh effort per post: - Light refresh: Update statistics, check links (1-2 hours) - Moderate refresh: Rewrite sections, add new data (3-4 hours) - Heavy refresh: Full rewrite recommended (5+ hours)
### Step 6: Generate Site-Wide Report
Aggregate all results into a comprehensive report:
#### Summary Dashboard ``` ## Blog Audit Report
**Audit Date:** [date] **Total Posts:** N **Average Score:** XX/100
### Health Overview | Metric | Count | |--------|-------| | Posts Scoring 90+ (Excellent) | N | | Posts Scoring 70-89 (Good) | N | | Posts Scoring 50-69 (Needs Work) | N | | Posts Scoring <50 (Poor) | N | | Orphan Pages | N | | Dead-End Pages | N | | Cannibalization Issues | N | | Stale or Decaying Content | N | ```
#### Per-Post Table ``` ### Per-Post Scores | Post | Score | Content | SEO | E-E-A-T | Technical | AI Citation | Issues | |------|-------|---------|-----|---------|-----------|-------------|--------| | [filename] | XX/100 | X/30 | X/25 | X/15 | X/15 | X/15 | [count] | ```
#### Prioritized Action Queue ``` ### Prioritized Action Queue (Lowest Score First) | Priority | Post | Score | Top Issue | Recommended Action | |----------|------|-------|-----------|--------------------| | 1 | [file] | XX | [issue] | [action] | | 2 | [file] | XX | [issue] | [action] | ```
#### Cannibalization Report ``` ### Topic Cannibalization | Keyword | Competing Posts | Recommendation | |---------|----------------|----------------| | [keyword] | post-a.md, post-b.md | Merge / Redirect / Differentiate | ```
#### Orphan Pages ``` ### Orphan Pages (No Inbound Links) | Page | Inbound Links | Recommended Link Sources | |------|---------------|--------------------------| | [file] | 0 | post-a.md, post-b.md, post-c.md | ```
#### Stale Content ``` ### Stale Content | Post | Last Updated | Days Stale | Priority | Refresh Effort | |------|-------------|------------|----------|----------------| | [file] | [date] | [N] | High/Med/Low | Light/Moderate/Heavy | ```
### Step 7: Save Report
Save timestamped Markdown and JSON exports under `reports/`, for example `reports/blog-audit-YYYY-MM-DD.md` and `reports/blog-audit-YYYY-MM-DD.json`. Do not overwrite a previous audit report.
After saving, inform the user: - Report locations: `[project-root]/reports/blog-audit-YYYY-MM-DD.md` and `[project-root]/reports/blog-audit-YYYY-MM-DD.json` - Summary of findings (total posts, average score, critical issues count) - Suggest running `/blog analyze <file>` on the lowest-scoring post first - Suggest running `/blog flow optimize` for AI-citation SEO checks on key posts
## Cross-reference
For evidence-led audit prompts beyond this site-wide health pass, see `/blog flow optimize` (visibility, CTR, schema, extraction audits) and `/blog flow win` (dual-surface scorecard, conversion audit).
Source provenance
Decision snapshot
2,016 GitHub stars
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for blog-audit, ready for a manual X post.
blog-audit: Full-site blog health assessment scanning all blog files for quality scores, orphan pages, to... 2.0K stars https://www.openagentskill.com/skills/agricidaniel-blog-audit?ref=x
Listing + install path for blog-audit: https://www.openagentskill.com/skills/agricidaniel-blog-audit?ref=x Install: npx skills add AgriciDaniel/claude-blog --skill blog-audit
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to AgriciDaniel but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/agricidaniel-blog-audit?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/agricidaniel-blog-audit?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/agricidaniel-blog-audit/audit)
[](https://www.openagentskill.com/skills/agricidaniel-blog-audit?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)AgriciDaniel
@agricidaniel
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
Wazuh
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
16.3K StarsMaigret
🕵️♂️ Collect a dossier on a person by username from 3000+ sites
32.9K StarsNuclei
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
29.2K StarsInfisical
Infisical is the open-source platform for secrets, certificates, and privileged access management.
27.4K StarsSandbox only
Install targets
Codex install prompt
Install the "blog-audit" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/brain/.raw/sources/claude-blog-skill/skills/blog-audit. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Full-site blog health assessment scanning all blog files for quality scores, orphan pages, topic cannibalization, stale content, and AI citation readiness. Runs canonical batch analysis before site-wide checks. Produces per-post scores and a prioritized action queue. Use when user says "audit blog", "blog audit", "site audit", "blog health", "audit all posts", "check all blogs". After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"agricidaniel-blog-audit","task":"Install blog-audit","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
Research agents
I need my agent to research a topic, compare sources, and produce a concise report.
Agent fit
Claude Code + OpenAI Agents + CLI
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add AgriciDaniel/claude-blog --skill blog-audit
Maintenance
fresh
8d since push
Risk
Needs review
Dependency or permission surface needs review
GitHub quality
2.0K
80/100 Quality · 77/100 Trust
Coverage tags
Review notes
Dependency or permission surface needs review · Permission surface may require sandboxing
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
StrongSolid option that is likely worth shortlisting for production workflows.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
2.0K GitHub stars
Repo activity
2.0K stars, 333 forks
Maintenance
8d since push
License
MIT
Install
npx skills add AgriciDaniel/claude-blog --skill blog-audit
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add AgriciDaniel/claude-blog --skill blog-auditDo not use when
Agent safety v2
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
Test manually in an isolated workspace and compare against safer alternatives.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
high
Skill metadata references credentials, tokens, environment variables, or secret-bearing workflows.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20blog-audit%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20blog-audit%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/agricidaniel-blog-audit/install
Agent should check
Copy prompt
Task: Use blog-audit in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20blog-audit%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/agricidaniel-blog-audit/install
Install command: npx skills add AgriciDaniel/claude-blog --skill blog-audit
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/agricidaniel-blog-audit/install
LLM text format
/api/skills/agricidaniel-blog-audit/install?format=text
Find alternatives
/api/skills/search?q=blog-audit&limit=3
Agent prompt
Use blog-audit for this task. Review https://www.openagentskill.com/api/skills/agricidaniel-blog-audit/install, then install with: npx skills add AgriciDaniel/claude-blog --skill blog-auditRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/agricidaniel-blog-audit
LLM text
/api/registry/manifest/agricidaniel-blog-audit?format=text
Install alias
/api/registry/install/agricidaniel-blog-audit
Recommend
/api/registry/recommend?task=Use%20blog-audit%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Use-case tags
Platforms
Claude Code, OpenAI Agents
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Role in stack
Primary pick
Primary fit
Research agents
Trust label
Production-ready
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
PASS2.0K GitHub stars
Stars/forks activity
PASS2.0K stars, 333 forks; issue activity unavailable in current metadata
Recent maintenance
PASS8d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Solid option that is likely worth shortlisting for production workflows.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Manage repositories
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Publish consistently
I need my agent to turn research and product updates into useful content drafts.
Workflow fit
Scrape, clean, and reuse web data
A practical workflow for agents that crawl public pages, extract clean content, normalize data, and hand it to downstream research or RAG workflows.
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Ingest, retrieve, and cite
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Alternative shortlist
Similar skills that may fit this task.
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
🕵️♂️ Collect a dossier on a person by username from 3000+ sites
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
Infisical is the open-source platform for secrets, certificates, and privileged access management.
--- name: blog-audit description: > Full-site blog health assessment scanning all blog files for quality scores, orphan pages, topic cannibalization, stale content, and AI citation readiness. Runs canonical batch analysis before site-wide checks. Produces per-post scores and a prioritized action queue. Use when user says "audit blog", "blog audit", "site audit", "blog health", "audit all posts", "check all blogs". user-invokable: true argument-hint: "[directory]" license: MIT ---
# Blog Audit: Full-Site Health Assessment
Performs a comprehensive blog health assessment across all posts in the project. Scans for quality scores, orphan pages, topic cannibalization, stale content, and AI citation readiness. Uses the canonical analyzer JSON as the score source and produces a prioritized action queue.
## Audit Process
### Step 1: Discover Blog Files
Scan the project for all blog content files:
- Recursively glob for `.md`, `.mdx`, `.html`, `.astro`, `.svelte`, `.vue`, `.tsx`, and `.jsx` in common blog directories and CMS export folders - Common paths to check: - `content/` - `posts/` - `blog/` - `src/content/` - `_posts/` - `pages/blog/` - `articles/` - `content/blog/**` - CMS export folders explicitly provided by the user - `src/pages/blog/` - Filter out hidden, vendor, generated, and secret-adjacent paths: `.git/`, dot-directories, `node_modules/`, `vendor/`, `dist/`, `build/`, `.next/`, `coverage/`, `reports/`, generated exports, README, CHANGELOG, LICENSE, config files, SKILL.md, package files, `.env*`, keys, and private notes - Report: "Found N blog files in [directories]"
If no blog files are found in standard locations, ask for an allow-listed root or only search user-approved content directories. Do not scan the entire project root by default.
### Step 2: Canonical Batch Analysis
Run canonical analyzer output first and use it as the source of per-post scores:
```bash python3 scripts/analyze_blog.py <blog-root> --batch --format json ```
Process files in chunks, cap parallel follow-up work to a small fixed number, respect context limits, and aggregate deterministic JSON with `file`, `score`, `categories`, `issues`, and `metadata`. Layer the site-wide checks below on top of analyzer JSON, not separate scoring rubrics.
#### Content Quality Layer - Score each post on the 30-point content quality scale - Check paragraph length (target 40-80 words, hard limit 150) - Check sentence length (target 15-20 words) - Evaluate heading structure and question-format headings - Assess readability using persona and content type: consumer content favors easier bands, professional content can be moderate, and technical content may be denser when clarity remains high
#### SEO Optimization Layer - Check on-page SEO elements per post: - Title tag length (40-60 acceptable, 50-60 ideal, preview warning only) - Meta description is concise and page-specific. Statistics are optional and must be visible and sourced - H1 presence and uniqueness - Image alt text coverage - Internal and external link counts - URL slug quality
#### Schema Validation Layer - Detect structured data across all posts - Validate Article/BlogPosting, Person, Organization, and BreadcrumbList schema completeness - If FAQPage exists, validate it as optional entity markup only, not a Google rich result - Normalize `dateModified`, `lastUpdated`, `updated`, and `lastmod`, including timezone-normalized generated schema, then require freshness parity - Flag missing or malformed schema
#### Link Health Layer - Map internal links across all posts - Build a directed link graph - Detect orphan pages (zero inbound internal links) - Detect dead-end pages (zero outbound internal links) - Check for broken internal link targets - Recommend bidirectional link opportunities
#### Freshness Check Layer - Read lastUpdated or dateModified from each post's frontmatter - Calculate days since last update - Flag freshness by content type, source or statistic age, and GSC decay, not by a universal day count - Categorize by refresh priority
#### AI Readiness Layer - Score each post for AI citation readiness - Check passage-level citability (120-180 word sections) - Evaluate Q&A formatting and entity clarity - Check for TL;DR boxes and citation capsules - Check robots.txt, llms.txt, SSR/SSG output, JS-gated content, blocked assets, GPTBot, ClaudeBot, PerplexityBot, Googlebot, and Google-Extended policies
### Step 2.5: Technical Crawl and Search Performance
Add site-wide technical checks before final recommendations:
- Validate sitemap coverage, robots.txt, noindex directives, canonical tags, redirects, HTTP status codes, hreflang, and internal canonical consistency - Use `blog-google` when available for Core Web Vitals, GSC queries, URL Inspection, indexing status, and GA4 context - Report skipped optional checks with reasons such as `SKIPPED: credentials unavailable`
### Step 3: Topic Cannibalization Detection
Analyze across all posts for keyword competition:
1. Extract primary keyword/topic from each post: - Title text - H1 heading - Meta description - First paragraph 2. Normalize keywords with stopword handling, lemmatization, locale awareness, and intent modifiers 3. Cluster by intent using analyzer data, embeddings or explicit confidence, GSC query-to-URL data when available, and SERP overlap where available 4. Flag competing posts with one of these recommendations: - **Merge**: Combine two weak posts into one strong post - **Redirect**: 301 redirect the weaker post to the stronger one after preserving backlinks, validating a redirect map, and updating internal links - **Differentiate**: Adjust focus so posts target distinct intents
### Step 4: Orphan Page Detection
Build and analyze the internal link graph:
1. Normalize URLs against site config and sitemap, including relative links, same-domain absolutes, trailing slashes, generated routes, anchors, and slug mappings 2. Build an adjacency map: `{ page -> [pages it links to] }` 3. Build a reverse map: `{ page -> [pages linking to it] }` 4. Identify orphan pages: posts with zero inbound internal links 5. Identify dead-end pages: posts with zero outbound internal links 6. For each orphan, recommend 2-3 existing posts that should link to it based on topic relevance
### Step 5: Stale Content Detection
Audit content freshness across all posts:
1. Read frontmatter fields: `lastUpdated`, `dateModified`, `date`, `updated` 2. Calculate days since last update for each post 3. Categorize by refresh priority: - **High**: Volatile topic, stale sources or statistics, or GSC decay - **Medium**: Evergreen topic with aging examples, links, or screenshots - **Low**: Recently validated or stable reference content 4. Estimate refresh effort per post: - Light refresh: Update statistics, check links (1-2 hours) - Moderate refresh: Rewrite sections, add new data (3-4 hours) - Heavy refresh: Full rewrite recommended (5+ hours)
### Step 6: Generate Site-Wide Report
Aggregate all results into a comprehensive report:
#### Summary Dashboard ``` ## Blog Audit Report
**Audit Date:** [date] **Total Posts:** N **Average Score:** XX/100
### Health Overview | Metric | Count | |--------|-------| | Posts Scoring 90+ (Excellent) | N | | Posts Scoring 70-89 (Good) | N | | Posts Scoring 50-69 (Needs Work) | N | | Posts Scoring <50 (Poor) | N | | Orphan Pages | N | | Dead-End Pages | N | | Cannibalization Issues | N | | Stale or Decaying Content | N | ```
#### Per-Post Table ``` ### Per-Post Scores | Post | Score | Content | SEO | E-E-A-T | Technical | AI Citation | Issues | |------|-------|---------|-----|---------|-----------|-------------|--------| | [filename] | XX/100 | X/30 | X/25 | X/15 | X/15 | X/15 | [count] | ```
#### Prioritized Action Queue ``` ### Prioritized Action Queue (Lowest Score First) | Priority | Post | Score | Top Issue | Recommended Action | |----------|------|-------|-----------|--------------------| | 1 | [file] | XX | [issue] | [action] | | 2 | [file] | XX | [issue] | [action] | ```
#### Cannibalization Report ``` ### Topic Cannibalization | Keyword | Competing Posts | Recommendation | |---------|----------------|----------------| | [keyword] | post-a.md, post-b.md | Merge / Redirect / Differentiate | ```
#### Orphan Pages ``` ### Orphan Pages (No Inbound Links) | Page | Inbound Links | Recommended Link Sources | |------|---------------|--------------------------| | [file] | 0 | post-a.md, post-b.md, post-c.md | ```
#### Stale Content ``` ### Stale Content | Post | Last Updated | Days Stale | Priority | Refresh Effort | |------|-------------|------------|----------|----------------| | [file] | [date] | [N] | High/Med/Low | Light/Moderate/Heavy | ```
### Step 7: Save Report
Save timestamped Markdown and JSON exports under `reports/`, for example `reports/blog-audit-YYYY-MM-DD.md` and `reports/blog-audit-YYYY-MM-DD.json`. Do not overwrite a previous audit report.
After saving, inform the user: - Report locations: `[project-root]/reports/blog-audit-YYYY-MM-DD.md` and `[project-root]/reports/blog-audit-YYYY-MM-DD.json` - Summary of findings (total posts, average score, critical issues count) - Suggest running `/blog analyze <file>` on the lowest-scoring post first - Suggest running `/blog flow optimize` for AI-citation SEO checks on key posts
## Cross-reference
For evidence-led audit prompts beyond this site-wide health pass, see `/blog flow optimize` (visibility, CTR, schema, extraction audits) and `/blog flow win` (dual-surface scorecard, conversion audit).
Source provenance
Decision snapshot
2,016 GitHub stars
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for blog-audit, ready for a manual X post.
blog-audit: Full-site blog health assessment scanning all blog files for quality scores, orphan pages, to... 2.0K stars https://www.openagentskill.com/skills/agricidaniel-blog-audit?ref=x
Listing + install path for blog-audit: https://www.openagentskill.com/skills/agricidaniel-blog-audit?ref=x Install: npx skills add AgriciDaniel/claude-blog --skill blog-audit
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to AgriciDaniel but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/agricidaniel-blog-audit?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/agricidaniel-blog-audit?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/agricidaniel-blog-audit/audit)
[](https://www.openagentskill.com/skills/agricidaniel-blog-audit?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)AgriciDaniel
@agricidaniel
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
Wazuh
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
16.3K StarsMaigret
🕵️♂️ Collect a dossier on a person by username from 3000+ sites
32.9K StarsNuclei
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
29.2K StarsInfisical
Infisical is the open-source platform for secrets, certificates, and privileged access management.
27.4K StarsSandbox only
Install targets
Codex install prompt
Install the "blog-audit" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/brain/.raw/sources/claude-blog-skill/skills/blog-audit. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Full-site blog health assessment scanning all blog files for quality scores, orphan pages, topic cannibalization, stale content, and AI citation readiness. Runs canonical batch analysis before site-wide checks. Produces per-post scores and a prioritized action queue. Use when user says "audit blog", "blog audit", "site audit", "blog health", "audit all posts", "check all blogs". After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"agricidaniel-blog-audit","task":"Install blog-audit","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
Research agents
I need my agent to research a topic, compare sources, and produce a concise report.
Agent fit
Claude Code + OpenAI Agents + CLI
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add AgriciDaniel/claude-blog --skill blog-audit
Maintenance
fresh
8d since push
Risk
Needs review
Dependency or permission surface needs review
GitHub quality
2.0K
80/100 Quality · 77/100 Trust
Coverage tags
Review notes
Dependency or permission surface needs review · Permission surface may require sandboxing
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
StrongSolid option that is likely worth shortlisting for production workflows.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
2.0K GitHub stars
Repo activity
2.0K stars, 333 forks
Maintenance
8d since push
License
MIT
Install
npx skills add AgriciDaniel/claude-blog --skill blog-audit
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add AgriciDaniel/claude-blog --skill blog-auditDo not use when
Agent safety v2
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
Test manually in an isolated workspace and compare against safer alternatives.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
high
Skill metadata references credentials, tokens, environment variables, or secret-bearing workflows.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20blog-audit%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20blog-audit%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/agricidaniel-blog-audit/install
Agent should check
Copy prompt
Task: Use blog-audit in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20blog-audit%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/agricidaniel-blog-audit/install
Install command: npx skills add AgriciDaniel/claude-blog --skill blog-audit
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/agricidaniel-blog-audit/install
LLM text format
/api/skills/agricidaniel-blog-audit/install?format=text
Find alternatives
/api/skills/search?q=blog-audit&limit=3
Agent prompt
Use blog-audit for this task. Review https://www.openagentskill.com/api/skills/agricidaniel-blog-audit/install, then install with: npx skills add AgriciDaniel/claude-blog --skill blog-auditRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/agricidaniel-blog-audit
LLM text
/api/registry/manifest/agricidaniel-blog-audit?format=text
Install alias
/api/registry/install/agricidaniel-blog-audit
Recommend
/api/registry/recommend?task=Use%20blog-audit%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Use-case tags
Platforms
Claude Code, OpenAI Agents
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Role in stack
Primary pick
Primary fit
Research agents
Trust label
Production-ready
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
PASS2.0K GitHub stars
Stars/forks activity
PASS2.0K stars, 333 forks; issue activity unavailable in current metadata
Recent maintenance
PASS8d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Solid option that is likely worth shortlisting for production workflows.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Manage repositories
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Publish consistently
I need my agent to turn research and product updates into useful content drafts.
Workflow fit
Scrape, clean, and reuse web data
A practical workflow for agents that crawl public pages, extract clean content, normalize data, and hand it to downstream research or RAG workflows.
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Ingest, retrieve, and cite
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Alternative shortlist
Similar skills that may fit this task.
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
🕵️♂️ Collect a dossier on a person by username from 3000+ sites
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
Infisical is the open-source platform for secrets, certificates, and privileged access management.
--- name: blog-audit description: > Full-site blog health assessment scanning all blog files for quality scores, orphan pages, topic cannibalization, stale content, and AI citation readiness. Runs canonical batch analysis before site-wide checks. Produces per-post scores and a prioritized action queue. Use when user says "audit blog", "blog audit", "site audit", "blog health", "audit all posts", "check all blogs". user-invokable: true argument-hint: "[directory]" license: MIT ---
# Blog Audit: Full-Site Health Assessment
Performs a comprehensive blog health assessment across all posts in the project. Scans for quality scores, orphan pages, topic cannibalization, stale content, and AI citation readiness. Uses the canonical analyzer JSON as the score source and produces a prioritized action queue.
## Audit Process
### Step 1: Discover Blog Files
Scan the project for all blog content files:
- Recursively glob for `.md`, `.mdx`, `.html`, `.astro`, `.svelte`, `.vue`, `.tsx`, and `.jsx` in common blog directories and CMS export folders - Common paths to check: - `content/` - `posts/` - `blog/` - `src/content/` - `_posts/` - `pages/blog/` - `articles/` - `content/blog/**` - CMS export folders explicitly provided by the user - `src/pages/blog/` - Filter out hidden, vendor, generated, and secret-adjacent paths: `.git/`, dot-directories, `node_modules/`, `vendor/`, `dist/`, `build/`, `.next/`, `coverage/`, `reports/`, generated exports, README, CHANGELOG, LICENSE, config files, SKILL.md, package files, `.env*`, keys, and private notes - Report: "Found N blog files in [directories]"
If no blog files are found in standard locations, ask for an allow-listed root or only search user-approved content directories. Do not scan the entire project root by default.
### Step 2: Canonical Batch Analysis
Run canonical analyzer output first and use it as the source of per-post scores:
```bash python3 scripts/analyze_blog.py <blog-root> --batch --format json ```
Process files in chunks, cap parallel follow-up work to a small fixed number, respect context limits, and aggregate deterministic JSON with `file`, `score`, `categories`, `issues`, and `metadata`. Layer the site-wide checks below on top of analyzer JSON, not separate scoring rubrics.
#### Content Quality Layer - Score each post on the 30-point content quality scale - Check paragraph length (target 40-80 words, hard limit 150) - Check sentence length (target 15-20 words) - Evaluate heading structure and question-format headings - Assess readability using persona and content type: consumer content favors easier bands, professional content can be moderate, and technical content may be denser when clarity remains high
#### SEO Optimization Layer - Check on-page SEO elements per post: - Title tag length (40-60 acceptable, 50-60 ideal, preview warning only) - Meta description is concise and page-specific. Statistics are optional and must be visible and sourced - H1 presence and uniqueness - Image alt text coverage - Internal and external link counts - URL slug quality
#### Schema Validation Layer - Detect structured data across all posts - Validate Article/BlogPosting, Person, Organization, and BreadcrumbList schema completeness - If FAQPage exists, validate it as optional entity markup only, not a Google rich result - Normalize `dateModified`, `lastUpdated`, `updated`, and `lastmod`, including timezone-normalized generated schema, then require freshness parity - Flag missing or malformed schema
#### Link Health Layer - Map internal links across all posts - Build a directed link graph - Detect orphan pages (zero inbound internal links) - Detect dead-end pages (zero outbound internal links) - Check for broken internal link targets - Recommend bidirectional link opportunities
#### Freshness Check Layer - Read lastUpdated or dateModified from each post's frontmatter - Calculate days since last update - Flag freshness by content type, source or statistic age, and GSC decay, not by a universal day count - Categorize by refresh priority
#### AI Readiness Layer - Score each post for AI citation readiness - Check passage-level citability (120-180 word sections) - Evaluate Q&A formatting and entity clarity - Check for TL;DR boxes and citation capsules - Check robots.txt, llms.txt, SSR/SSG output, JS-gated content, blocked assets, GPTBot, ClaudeBot, PerplexityBot, Googlebot, and Google-Extended policies
### Step 2.5: Technical Crawl and Search Performance
Add site-wide technical checks before final recommendations:
- Validate sitemap coverage, robots.txt, noindex directives, canonical tags, redirects, HTTP status codes, hreflang, and internal canonical consistency - Use `blog-google` when available for Core Web Vitals, GSC queries, URL Inspection, indexing status, and GA4 context - Report skipped optional checks with reasons such as `SKIPPED: credentials unavailable`
### Step 3: Topic Cannibalization Detection
Analyze across all posts for keyword competition:
1. Extract primary keyword/topic from each post: - Title text - H1 heading - Meta description - First paragraph 2. Normalize keywords with stopword handling, lemmatization, locale awareness, and intent modifiers 3. Cluster by intent using analyzer data, embeddings or explicit confidence, GSC query-to-URL data when available, and SERP overlap where available 4. Flag competing posts with one of these recommendations: - **Merge**: Combine two weak posts into one strong post - **Redirect**: 301 redirect the weaker post to the stronger one after preserving backlinks, validating a redirect map, and updating internal links - **Differentiate**: Adjust focus so posts target distinct intents
### Step 4: Orphan Page Detection
Build and analyze the internal link graph:
1. Normalize URLs against site config and sitemap, including relative links, same-domain absolutes, trailing slashes, generated routes, anchors, and slug mappings 2. Build an adjacency map: `{ page -> [pages it links to] }` 3. Build a reverse map: `{ page -> [pages linking to it] }` 4. Identify orphan pages: posts with zero inbound internal links 5. Identify dead-end pages: posts with zero outbound internal links 6. For each orphan, recommend 2-3 existing posts that should link to it based on topic relevance
### Step 5: Stale Content Detection
Audit content freshness across all posts:
1. Read frontmatter fields: `lastUpdated`, `dateModified`, `date`, `updated` 2. Calculate days since last update for each post 3. Categorize by refresh priority: - **High**: Volatile topic, stale sources or statistics, or GSC decay - **Medium**: Evergreen topic with aging examples, links, or screenshots - **Low**: Recently validated or stable reference content 4. Estimate refresh effort per post: - Light refresh: Update statistics, check links (1-2 hours) - Moderate refresh: Rewrite sections, add new data (3-4 hours) - Heavy refresh: Full rewrite recommended (5+ hours)
### Step 6: Generate Site-Wide Report
Aggregate all results into a comprehensive report:
#### Summary Dashboard ``` ## Blog Audit Report
**Audit Date:** [date] **Total Posts:** N **Average Score:** XX/100
### Health Overview | Metric | Count | |--------|-------| | Posts Scoring 90+ (Excellent) | N | | Posts Scoring 70-89 (Good) | N | | Posts Scoring 50-69 (Needs Work) | N | | Posts Scoring <50 (Poor) | N | | Orphan Pages | N | | Dead-End Pages | N | | Cannibalization Issues | N | | Stale or Decaying Content | N | ```
#### Per-Post Table ``` ### Per-Post Scores | Post | Score | Content | SEO | E-E-A-T | Technical | AI Citation | Issues | |------|-------|---------|-----|---------|-----------|-------------|--------| | [filename] | XX/100 | X/30 | X/25 | X/15 | X/15 | X/15 | [count] | ```
#### Prioritized Action Queue ``` ### Prioritized Action Queue (Lowest Score First) | Priority | Post | Score | Top Issue | Recommended Action | |----------|------|-------|-----------|--------------------| | 1 | [file] | XX | [issue] | [action] | | 2 | [file] | XX | [issue] | [action] | ```
#### Cannibalization Report ``` ### Topic Cannibalization | Keyword | Competing Posts | Recommendation | |---------|----------------|----------------| | [keyword] | post-a.md, post-b.md | Merge / Redirect / Differentiate | ```
#### Orphan Pages ``` ### Orphan Pages (No Inbound Links) | Page | Inbound Links | Recommended Link Sources | |------|---------------|--------------------------| | [file] | 0 | post-a.md, post-b.md, post-c.md | ```
#### Stale Content ``` ### Stale Content | Post | Last Updated | Days Stale | Priority | Refresh Effort | |------|-------------|------------|----------|----------------| | [file] | [date] | [N] | High/Med/Low | Light/Moderate/Heavy | ```
### Step 7: Save Report
Save timestamped Markdown and JSON exports under `reports/`, for example `reports/blog-audit-YYYY-MM-DD.md` and `reports/blog-audit-YYYY-MM-DD.json`. Do not overwrite a previous audit report.
After saving, inform the user: - Report locations: `[project-root]/reports/blog-audit-YYYY-MM-DD.md` and `[project-root]/reports/blog-audit-YYYY-MM-DD.json` - Summary of findings (total posts, average score, critical issues count) - Suggest running `/blog analyze <file>` on the lowest-scoring post first - Suggest running `/blog flow optimize` for AI-citation SEO checks on key posts
## Cross-reference
For evidence-led audit prompts beyond this site-wide health pass, see `/blog flow optimize` (visibility, CTR, schema, extraction audits) and `/blog flow win` (dual-surface scorecard, conversion audit).
Source provenance
Decision snapshot
2,016 GitHub stars
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for blog-audit, ready for a manual X post.
blog-audit: Full-site blog health assessment scanning all blog files for quality scores, orphan pages, to... 2.0K stars https://www.openagentskill.com/skills/agricidaniel-blog-audit?ref=x
Listing + install path for blog-audit: https://www.openagentskill.com/skills/agricidaniel-blog-audit?ref=x Install: npx skills add AgriciDaniel/claude-blog --skill blog-audit
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to AgriciDaniel but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/agricidaniel-blog-audit?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/agricidaniel-blog-audit?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/agricidaniel-blog-audit/audit)
[](https://www.openagentskill.com/skills/agricidaniel-blog-audit?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)AgriciDaniel
@agricidaniel
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
Wazuh
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
16.3K StarsMaigret
🕵️♂️ Collect a dossier on a person by username from 3000+ sites
32.9K StarsNuclei
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
29.2K StarsInfisical
Infisical is the open-source platform for secrets, certificates, and privileged access management.
27.4K StarsSandbox only
Install targets
Codex install prompt
Install the "blog-audit" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/brain/.raw/sources/claude-blog-skill/skills/blog-audit. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Full-site blog health assessment scanning all blog files for quality scores, orphan pages, topic cannibalization, stale content, and AI citation readiness. Runs canonical batch analysis before site-wide checks. Produces per-post scores and a prioritized action queue. Use when user says "audit blog", "blog audit", "site audit", "blog health", "audit all posts", "check all blogs". After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"agricidaniel-blog-audit","task":"Install blog-audit","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
Research agents
I need my agent to research a topic, compare sources, and produce a concise report.
Agent fit
Claude Code + OpenAI Agents + CLI
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add AgriciDaniel/claude-blog --skill blog-audit
Maintenance
fresh
8d since push
Risk
Needs review
Dependency or permission surface needs review
GitHub quality
2.0K
80/100 Quality · 77/100 Trust
Coverage tags
Review notes
Dependency or permission surface needs review · Permission surface may require sandboxing
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
StrongSolid option that is likely worth shortlisting for production workflows.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
2.0K GitHub stars
Repo activity
2.0K stars, 333 forks
Maintenance
8d since push
License
MIT
Install
npx skills add AgriciDaniel/claude-blog --skill blog-audit
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add AgriciDaniel/claude-blog --skill blog-auditDo not use when
Agent safety v2
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
Test manually in an isolated workspace and compare against safer alternatives.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
high
Skill metadata references credentials, tokens, environment variables, or secret-bearing workflows.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20blog-audit%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20blog-audit%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/agricidaniel-blog-audit/install
Agent should check
Copy prompt
Task: Use blog-audit in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20blog-audit%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/agricidaniel-blog-audit/install
Install command: npx skills add AgriciDaniel/claude-blog --skill blog-audit
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/agricidaniel-blog-audit/install
LLM text format
/api/skills/agricidaniel-blog-audit/install?format=text
Find alternatives
/api/skills/search?q=blog-audit&limit=3
Agent prompt
Use blog-audit for this task. Review https://www.openagentskill.com/api/skills/agricidaniel-blog-audit/install, then install with: npx skills add AgriciDaniel/claude-blog --skill blog-auditRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/agricidaniel-blog-audit
LLM text
/api/registry/manifest/agricidaniel-blog-audit?format=text
Install alias
/api/registry/install/agricidaniel-blog-audit
Recommend
/api/registry/recommend?task=Use%20blog-audit%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Use-case tags
Platforms
Claude Code, OpenAI Agents
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Role in stack
Primary pick
Primary fit
Research agents
Trust label
Production-ready
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
PASS2.0K GitHub stars
Stars/forks activity
PASS2.0K stars, 333 forks; issue activity unavailable in current metadata
Recent maintenance
PASS8d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Solid option that is likely worth shortlisting for production workflows.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Manage repositories
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Publish consistently
I need my agent to turn research and product updates into useful content drafts.
Workflow fit
Scrape, clean, and reuse web data
A practical workflow for agents that crawl public pages, extract clean content, normalize data, and hand it to downstream research or RAG workflows.
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Ingest, retrieve, and cite
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Alternative shortlist
Similar skills that may fit this task.
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
🕵️♂️ Collect a dossier on a person by username from 3000+ sites
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
Infisical is the open-source platform for secrets, certificates, and privileged access management.
--- name: blog-audit description: > Full-site blog health assessment scanning all blog files for quality scores, orphan pages, topic cannibalization, stale content, and AI citation readiness. Runs canonical batch analysis before site-wide checks. Produces per-post scores and a prioritized action queue. Use when user says "audit blog", "blog audit", "site audit", "blog health", "audit all posts", "check all blogs". user-invokable: true argument-hint: "[directory]" license: MIT ---
# Blog Audit: Full-Site Health Assessment
Performs a comprehensive blog health assessment across all posts in the project. Scans for quality scores, orphan pages, topic cannibalization, stale content, and AI citation readiness. Uses the canonical analyzer JSON as the score source and produces a prioritized action queue.
## Audit Process
### Step 1: Discover Blog Files
Scan the project for all blog content files:
- Recursively glob for `.md`, `.mdx`, `.html`, `.astro`, `.svelte`, `.vue`, `.tsx`, and `.jsx` in common blog directories and CMS export folders - Common paths to check: - `content/` - `posts/` - `blog/` - `src/content/` - `_posts/` - `pages/blog/` - `articles/` - `content/blog/**` - CMS export folders explicitly provided by the user - `src/pages/blog/` - Filter out hidden, vendor, generated, and secret-adjacent paths: `.git/`, dot-directories, `node_modules/`, `vendor/`, `dist/`, `build/`, `.next/`, `coverage/`, `reports/`, generated exports, README, CHANGELOG, LICENSE, config files, SKILL.md, package files, `.env*`, keys, and private notes - Report: "Found N blog files in [directories]"
If no blog files are found in standard locations, ask for an allow-listed root or only search user-approved content directories. Do not scan the entire project root by default.
### Step 2: Canonical Batch Analysis
Run canonical analyzer output first and use it as the source of per-post scores:
```bash python3 scripts/analyze_blog.py <blog-root> --batch --format json ```
Process files in chunks, cap parallel follow-up work to a small fixed number, respect context limits, and aggregate deterministic JSON with `file`, `score`, `categories`, `issues`, and `metadata`. Layer the site-wide checks below on top of analyzer JSON, not separate scoring rubrics.
#### Content Quality Layer - Score each post on the 30-point content quality scale - Check paragraph length (target 40-80 words, hard limit 150) - Check sentence length (target 15-20 words) - Evaluate heading structure and question-format headings - Assess readability using persona and content type: consumer content favors easier bands, professional content can be moderate, and technical content may be denser when clarity remains high
#### SEO Optimization Layer - Check on-page SEO elements per post: - Title tag length (40-60 acceptable, 50-60 ideal, preview warning only) - Meta description is concise and page-specific. Statistics are optional and must be visible and sourced - H1 presence and uniqueness - Image alt text coverage - Internal and external link counts - URL slug quality
#### Schema Validation Layer - Detect structured data across all posts - Validate Article/BlogPosting, Person, Organization, and BreadcrumbList schema completeness - If FAQPage exists, validate it as optional entity markup only, not a Google rich result - Normalize `dateModified`, `lastUpdated`, `updated`, and `lastmod`, including timezone-normalized generated schema, then require freshness parity - Flag missing or malformed schema
#### Link Health Layer - Map internal links across all posts - Build a directed link graph - Detect orphan pages (zero inbound internal links) - Detect dead-end pages (zero outbound internal links) - Check for broken internal link targets - Recommend bidirectional link opportunities
#### Freshness Check Layer - Read lastUpdated or dateModified from each post's frontmatter - Calculate days since last update - Flag freshness by content type, source or statistic age, and GSC decay, not by a universal day count - Categorize by refresh priority
#### AI Readiness Layer - Score each post for AI citation readiness - Check passage-level citability (120-180 word sections) - Evaluate Q&A formatting and entity clarity - Check for TL;DR boxes and citation capsules - Check robots.txt, llms.txt, SSR/SSG output, JS-gated content, blocked assets, GPTBot, ClaudeBot, PerplexityBot, Googlebot, and Google-Extended policies
### Step 2.5: Technical Crawl and Search Performance
Add site-wide technical checks before final recommendations:
- Validate sitemap coverage, robots.txt, noindex directives, canonical tags, redirects, HTTP status codes, hreflang, and internal canonical consistency - Use `blog-google` when available for Core Web Vitals, GSC queries, URL Inspection, indexing status, and GA4 context - Report skipped optional checks with reasons such as `SKIPPED: credentials unavailable`
### Step 3: Topic Cannibalization Detection
Analyze across all posts for keyword competition:
1. Extract primary keyword/topic from each post: - Title text - H1 heading - Meta description - First paragraph 2. Normalize keywords with stopword handling, lemmatization, locale awareness, and intent modifiers 3. Cluster by intent using analyzer data, embeddings or explicit confidence, GSC query-to-URL data when available, and SERP overlap where available 4. Flag competing posts with one of these recommendations: - **Merge**: Combine two weak posts into one strong post - **Redirect**: 301 redirect the weaker post to the stronger one after preserving backlinks, validating a redirect map, and updating internal links - **Differentiate**: Adjust focus so posts target distinct intents
### Step 4: Orphan Page Detection
Build and analyze the internal link graph:
1. Normalize URLs against site config and sitemap, including relative links, same-domain absolutes, trailing slashes, generated routes, anchors, and slug mappings 2. Build an adjacency map: `{ page -> [pages it links to] }` 3. Build a reverse map: `{ page -> [pages linking to it] }` 4. Identify orphan pages: posts with zero inbound internal links 5. Identify dead-end pages: posts with zero outbound internal links 6. For each orphan, recommend 2-3 existing posts that should link to it based on topic relevance
### Step 5: Stale Content Detection
Audit content freshness across all posts:
1. Read frontmatter fields: `lastUpdated`, `dateModified`, `date`, `updated` 2. Calculate days since last update for each post 3. Categorize by refresh priority: - **High**: Volatile topic, stale sources or statistics, or GSC decay - **Medium**: Evergreen topic with aging examples, links, or screenshots - **Low**: Recently validated or stable reference content 4. Estimate refresh effort per post: - Light refresh: Update statistics, check links (1-2 hours) - Moderate refresh: Rewrite sections, add new data (3-4 hours) - Heavy refresh: Full rewrite recommended (5+ hours)
### Step 6: Generate Site-Wide Report
Aggregate all results into a comprehensive report:
#### Summary Dashboard ``` ## Blog Audit Report
**Audit Date:** [date] **Total Posts:** N **Average Score:** XX/100
### Health Overview | Metric | Count | |--------|-------| | Posts Scoring 90+ (Excellent) | N | | Posts Scoring 70-89 (Good) | N | | Posts Scoring 50-69 (Needs Work) | N | | Posts Scoring <50 (Poor) | N | | Orphan Pages | N | | Dead-End Pages | N | | Cannibalization Issues | N | | Stale or Decaying Content | N | ```
#### Per-Post Table ``` ### Per-Post Scores | Post | Score | Content | SEO | E-E-A-T | Technical | AI Citation | Issues | |------|-------|---------|-----|---------|-----------|-------------|--------| | [filename] | XX/100 | X/30 | X/25 | X/15 | X/15 | X/15 | [count] | ```
#### Prioritized Action Queue ``` ### Prioritized Action Queue (Lowest Score First) | Priority | Post | Score | Top Issue | Recommended Action | |----------|------|-------|-----------|--------------------| | 1 | [file] | XX | [issue] | [action] | | 2 | [file] | XX | [issue] | [action] | ```
#### Cannibalization Report ``` ### Topic Cannibalization | Keyword | Competing Posts | Recommendation | |---------|----------------|----------------| | [keyword] | post-a.md, post-b.md | Merge / Redirect / Differentiate | ```
#### Orphan Pages ``` ### Orphan Pages (No Inbound Links) | Page | Inbound Links | Recommended Link Sources | |------|---------------|--------------------------| | [file] | 0 | post-a.md, post-b.md, post-c.md | ```
#### Stale Content ``` ### Stale Content | Post | Last Updated | Days Stale | Priority | Refresh Effort | |------|-------------|------------|----------|----------------| | [file] | [date] | [N] | High/Med/Low | Light/Moderate/Heavy | ```
### Step 7: Save Report
Save timestamped Markdown and JSON exports under `reports/`, for example `reports/blog-audit-YYYY-MM-DD.md` and `reports/blog-audit-YYYY-MM-DD.json`. Do not overwrite a previous audit report.
After saving, inform the user: - Report locations: `[project-root]/reports/blog-audit-YYYY-MM-DD.md` and `[project-root]/reports/blog-audit-YYYY-MM-DD.json` - Summary of findings (total posts, average score, critical issues count) - Suggest running `/blog analyze <file>` on the lowest-scoring post first - Suggest running `/blog flow optimize` for AI-citation SEO checks on key posts
## Cross-reference
For evidence-led audit prompts beyond this site-wide health pass, see `/blog flow optimize` (visibility, CTR, schema, extraction audits) and `/blog flow win` (dual-surface scorecard, conversion audit).
Source provenance
Decision snapshot
2,016 GitHub stars
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for blog-audit, ready for a manual X post.
blog-audit: Full-site blog health assessment scanning all blog files for quality scores, orphan pages, to... 2.0K stars https://www.openagentskill.com/skills/agricidaniel-blog-audit?ref=x
Listing + install path for blog-audit: https://www.openagentskill.com/skills/agricidaniel-blog-audit?ref=x Install: npx skills add AgriciDaniel/claude-blog --skill blog-audit
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to AgriciDaniel but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/agricidaniel-blog-audit?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/agricidaniel-blog-audit?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/agricidaniel-blog-audit/audit)
[](https://www.openagentskill.com/skills/agricidaniel-blog-audit?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)AgriciDaniel
@agricidaniel
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
Wazuh
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
16.3K StarsMaigret
🕵️♂️ Collect a dossier on a person by username from 3000+ sites
32.9K StarsNuclei
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
29.2K StarsInfisical
Infisical is the open-source platform for secrets, certificates, and privileged access management.
27.4K StarsPermission surface
secrets or environment access, shell or command execution
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
secrets or environment access, shell or command execution
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
secrets or environment access, shell or command execution
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
secrets or environment access, shell or command execution
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness