index365usa/index365
Run Marketing Signal website scans from your coding agent, read prioritized findings across SEO, Content, AEO, Analytics and Tracking, Conversion, and Trust and Proof, and apply fixes with a re-scan for proof.
Use when the user mentions index365, has an i365_ API key, or wants to audit a website for how well it performs across SEO, Content, AEO (Answer Engine Optimization), Analytics and Tracking, Conversion, and Trust and Proof. Triggers: "audit my site", "check my AI visibility", "run an index365 audit", "what's my score", "how does my site score", "fix what index365 found", or a pasted finding / "copy fix prompt for your agent" button. This is the router: it picks the right index365 sub-skill. Do NOT trigger for unrelated SEO tools, generic web scraping, or local-file tasks.
Use when the user wants to start auditing a domain that index365 does not track yet.
Triggers: "add a site to index365", "start auditing yoursite.com", "track this domain",
"create an index365 project for…". Scanning a new domain creates its project in the
same command, so the usual answer is one scan. Use the explicit create only to
pre-register a domain without spending credits on a scan.
Use when the user wants to fix a single index365 finding in this repository. Triggers:
"fix this finding", a pasted findingId (e.g. f_ab12cd34), the "copy fix prompt for
your agent" button from the dashboard, "apply the index365 fix for…", or "resolve this
one issue". One finding, one focused diff. For the whole report at once, use
index365-audit-and-fix.
Use when the user wants their coding agent to audit their site with index365 AND fix what it finds in the current repo, not just report it. Triggers: "make my site AI-ready", "audit and fix my site", "fix everything index365 finds", "improve my index365 score", or the user pastes a report and says "act on this". This is the full autonomous loop. For a single finding use index365-apply-fix; to only read, use index365-read-report.
Use when the user wants to remove a project from index365. Triggers: "delete the
index365 project for…", "remove yoursite.com from index365", "stop tracking this site",
"clean up old projects". Removal archives the project and is reversible with
index365 projects restore, and it still requires exact-domain confirmation. Use this
skill whenever a removal is requested, never call index365 projects archive ad hoc.
Use when the user wants to see the results of an index365 scan without changing code. Triggers: "show my score", "what's wrong with my site", "read the audit report", "list the findings", "what did the audit find", "show the marketing signal report". Read-only: it reads and explains, it does not fix. To fix, use index365-apply-fix or index365-audit-and-fix.
Use when the user wants to run or re-run an index365 scan. Triggers: "run an audit", "scan my site", "check my score", "re-run the audit", "run a marketing signal audit", "audit yoursite.com again". Covers the Marketing Signal scan and async runs. A scan is a paid action, see below.
Use when index365 is being used for the first time, when any index365 command exits 3
or returns a 401 / auth error, when index365 doctor reports missing authentication,
or when the user says "connect index365", "set up index365", "log in to index365", or
"add my index365 API key". This is the recovery path for every other index365 skill.
Do not work around missing or insufficient authentication, fix it here.
Use when an index365 scan has findings and the user wants a plan before any code changes. Triggers: "what should I fix first", "prioritize the findings", "triage this audit", "turn the findings into a plan", "which of these matter". Produces a prioritized, file-mapped fix plan. It plans only, it does not edit code (use index365-apply-fix or index365-audit-and-fix to apply).