Individual skill
anycap-ai-tool-seo
Audit and plan organic search for AI tool, SaaS, and product-led websites. Use for Search Console diagnosis, existing-page optimization, search intent and page ownership, technical indexing, content briefs, international SEO, citations, or programmatic SEO. Start with measured visibility and existing URLs before recommending new pages.
skills/anycap-ai-tool-seo/SKILL.md
Source commit a7ff827a4fef902c1874163c4ebb36edad6b9932
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 50
- Repository last updated
- Oct 21, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent Repository topic
- cli Repository topic
- skills Repository topic
- agent-skills Repository topic
- claude-code Repository topic
- coding-agent Repository topic
- marketing Derived category
- writing Derived category
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,955 bytesSKILL.mdcore · 5,955 bytesSKILL.mdcore · 5,955 bytesSKILL.mdcore · 5,955 bytesagents/openai.yamlasset · 281 bytesreferences/framework.mddoc · 3,602 bytesreferences/guardrails.mddoc · 3,984 bytesreferences/page-planning.mddoc · 2,818 bytes
Read excerpt
# AnyCap AI Tool SEO
Audit search visibility and decide what to fix, improve, consolidate, or publish next. A technically valid page is only eligible for indexing; it is not guaranteed to be crawled, indexed, or ranked.
Read [framework.md](references/framework.md), [page-planning.md](references/page-planning.md), and [guardrails.md](references/guardrails.md) before recommending site-wide changes. Use the current site and first-party evidence as the source of truth for its status.
## Workflow
### 1. Establish the baseline
- Identify the site, searcher, target market, conversion path, current URL inventory, and recently changed or retired URLs. Infer missing context from the site when possible.
- In Google Search Console (GSC), compare complete date ranges and page/query cohorts. Separate branded from non-branded searches and current URLs from retired URLs. Record impressions, clicks, index coverage, and the last complete data date. Do not infer that a past algorithmic visibility loss has ended solely because manual actions and security issues are clear.
- Use Ahrefs or similar tools for competitor discovery and keyword estimates; use GSC for the site's observed Google Search performance. Label estimates and time windows.
- If GSC is unavailable, say which conclusions remain unverified and continue with public crawling and site evidence.