--- title: "index365" description: "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." canonical: https://agentpluginsdirectory.com/plugins/index365 last-updated: 2026-09-22 --- # 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. - Slug: index365 - Publisher: index365 - Repository: https://github.com/index365usa/agent-skills - Manifest: plugin.json - Version: 0.1.0 - License: MIT - Category (editorial): integrations - Skills: 9 (index365-add-project, index365-apply-fix, index365-audit-and-fix, index365-delete-project, index365-read-report, index365-run-audit, index365-setup, index365-triage-findings, index365) - MCP servers: 1 (index365) - Stars: 1 - Repository created: 2026-06-18 - Repository last pushed: 2026-08-31 - Publisher type: Organization - Listing: https://agentpluginsdirectory.com/plugins/index365 - Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json ## What index365 does, in the publisher's words Power AI agents with intelligence. Agent Skills for index365, an agent-native website findings platform. Run a Marketing Signal scan on an authorized URL, read prioritized findings with evidence and remediation, make a bounded correction in the local project, and re-scan for proof. These skills wrap @index365/cli, which wraps the public /api/v1. The API owns product logic. Skills teach a coding agent which supported command to run and how to judge the result. - No command requires an id. Every read defaults to your latest completed run: index365 findings, index365 report, and index365 check take no arguments, and a domain narrows any of them to that site. index365 findings get 1 reads the first finding and prints a copy-pasteable fix prompt. - One question, at most. index365 scan yoursite.com resolves the project from the domain. A new domain asks exactly one [Y/n] question before creating the project and spending credits; --yes answers it for scripts, and a non-interactive shell never prompts. From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/index365usa/agent-skills/HEAD/README.md ## Skills - index365-add-project: 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 `… - index365-apply-fix: 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 d… - 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… - index365-delete-project: 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 ex… - index365-read-report: 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 fi… - index365-run-audit: 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. - index365-setup: 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 re… - index365-triage-findings: 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 do… - index365: 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… Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized. ## MCP servers - index365: transport: streamable-http; url: https://index365.co/api/mcp Read from the plugin's own mcp.json. Environment variable names only, never values.