AgentStack
SKILL verified MIT Self-run

Hoo Monthly Audit

skill-shalintripathi-organic-os-hoo-monthly-audit · by shalintripathi

Use for the monthly deep audit - "run the monthly audit", /organic-os:monthly-audit, or the scheduled monthly routine.

No reviews yet
0 installs
1 views
0.0% view→install

Install

$ agentstack add skill-shalintripathi-organic-os-hoo-monthly-audit

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Hoo Monthly Audit? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Monthly deep audit

  1. Full sweep via the orchestrator pattern: launch all eight specialists in

parallel with the profile path.

  1. Additionally: content freshness review (pages > 12 months stale that hold

rankings - freshness is a strong-evidence AEO factor), schema validity, internal-link health, tracked-keyword trend over the month, outcomes review (which applied changes moved metrics; feed wins/losses to the reflector). Run the page-essentials dimension (skills/onsite-audit step 3: author entity, answer capsule, in-content images, social image shape, publisher schema shape, sitemap membership) site-wide across the audited page set, not only on newly flagged pages - the checklist is the product's eyes, and a check that does not run cannot fire. The internal-link health line above runs as skills/onsite-audit step 4: one capped own-site crawl (onsite.linkgraph, sitemap-seeded) for broken links, orphans, hubs, shallow striking-distance pages, and redirect chains - same signal severities, same one-proposal cap.

  1. Compare with last month's runs/ artifacts; the report leads with deltas.
  2. File signals, briefs, and fixes through core contracts; rebuild queue;

notify per approval channel. Only send items where is_notified(item) is false; call mark_notified(path) right after a successful send.

  1. Output runs/YYYYMM-monthly/REPORT.md: executive summary in plain language,

then per-specialist sections, then this month's queued work.

At each stage boundary, append a one-line progress marker with a UTC timestamp to the run report file before starting the stage - headless runs are watched by tailing that file, not a terminal.

Entity consistency

  1. Build the property set from the profile: the site's own homepage and

about page, plus every URL in the optional brand.properties: list (a GitHub org or repo, a LinkedIn page - see site-repo-contract.md). Only URLs the profile provides are fetched - never guess a handle or search for unlisted profiles. No brand.properties: list means the check runs on the site's own pages only, and the report says so.

  1. Fetch each property (WebFetch of public pages within the session -

the sanctioned mechanism, docs/adr/0006 in the repo, same as the citation tracker) and extract the core brand facts each one states: brand name, one-line description, founding and location claims where stated, logo reference, and sameAs cross-links between properties.

  1. Compare across properties. Each inconsistency is one P2 signal per

fact: what differs, where (the URLs and their two values), and which version the profile says is canonical (the profile's site name and organization details are the reference; a fact the profile does not state has no canonical version - report the divergence, pick none).

  1. Route fixes by where they land: an inconsistency on the user's own

site becomes a gated proposal (a schema or about-page edit via create_item, through the normal approval gate); an inconsistency on a third-party property is a named human step in the report - this skill never writes off-site.

  1. Rationale line, carried next to this section's output: consistency

across authoritative sources drives inclusion in AI answers (https://www.useomnia.com/blog/how-to-improve-brand-visibility-chatgpt).

No web access this session: skip this section and note it as one line in REPORT.md ("entity consistency: skipped, no web access") instead of guessing.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.