agentsclimarketplace

Index365 triage findings

Skill index365usa/agent-skills/skills/index365-triage-findings

Request AI-Readiness and Marketing Signal scans and use prioritized findings from your coding agent.

Install
npx -y skills add index365usa/agent-skills --skill index365-triage-findings

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when an index365 audit 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).

SKILL.md

2.2 KB, as published. Nobody here has run it

index365 triage findings

Turn a completed run's findings into a prioritized, file-mapped plan. Planning only.

Prerequisite

A runId for a completed run, and (ideally) you are inside the repository that serves the audited site, so findings can map to files.

Workflow

  1. Pull the report to a file (don't dump it into context):

    mkdir -p .index365
index365 reports context run_xxx > .index365/report-run_xxx.json

  2. List findings worst-first:

    index365 findings list --run run_xxx --severity critical
index365 findings list --run run_xxx --severity high

  3. Rank over the file with a subagent. For a large report, dispatch a subagent to rank findings from .index365/report-run_xxx.json rather than loading the whole thing yourself. Order by user impact, group by category (or stage for Marketing Signal).

  4. Map each finding to repo files. Use affectedUrls + Glob/Grep to find the route/component/template that produces each affected URL. Note findings whose affectedUrls don't resolve to a file in this repo, those are out of scope for an in-repo fix.

  5. Output the plan (do not change code): an ordered list of findingId → title → severity → target file(s) → the remediation from the finding. Group into 1–3 reviewable batches, smallest safe diffs first. Flag anything that needs a human decision.

Shortcut via MCP prompts

If the index365 MCP server is connected, the triage_findings and prepare_pr_plan prompts do steps 2–5 directly. Use them when you're in an MCP host; otherwise the CLI flow above is equivalent.

Next

Apply the plan with index365-apply-fix (one finding at a time) or run the whole loop with index365-audit-and-fix.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.