Index365 delete project

Skill index365usa/agent-skills/skills/index365-delete-project

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-delete-project

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 the user wants to remove a project from index365. Triggers: "delete the index365 project for…", "remove example.com from index365", "stop tracking this site", "clean up old projects". This is the only destructive index365 action and it is irreversible. Use this skill whenever a delete is requested, never call `index365 projects delete` ad hoc.

SKILL.md

3.2 KB, as published. Nobody here has run it

index365 delete project

Permanently delete an index365 project.

Deleting a project is a hard, irreversible delete of the project record. Related project-scoped API keys, monitored assets, and monitoring events cascade. Run history is preserved with its project link cleared, so historical run findings remain available by run. There is no project recovery window or soft-delete. Treat it accordingly.

Iron rule

Never delete a project the user did not name by its exact domain in this conversation. You must read the project first and confirm the exact domain back to the user before deleting.

Workflow

Find it: read before destroy.
```
index365 projects list --json
```
Identify the single project the user means. If more than one could match, list the candidates and ask which one. Never guess.
Confirm the exact domain with the user. State what will be deleted and what is preserved:

"This permanently deletes the example.com project (projectId prj_…) and its project-scoped monitoring/configuration. Existing run history and findings are preserved without the project link. The project deletion cannot be undone. Confirm the domain to proceed." Wait for the user to confirm the exact domain.
Delete with the echo-confirm. The API requires the project's exact domain as --confirm; a mismatch is rejected (400). The CLI also re-reads the project first.
```
index365 projects delete prj_xxx --confirm example.com
```
Report what was deleted (domain + projectId).

Prerequisite

An authenticated credential with projects:delete. Current dashboard API keys carry the full work-area scope set, including create and delete. If the scope is absent, use index365-setup to reauthenticate through a supported path.

Red flags: STOP

The user said "delete all my projects" / "delete everything" / used a wildcard → refuse the bulk form. Delete one project at a time, each with its own confirmation.
You're about to pass --confirm with a domain you inferred rather than read from projects list → STOP, read it first.
You're tempted to skip the confirmation "because the user is in a hurry" → the confirmation is the safety; it stays.
You can't tell which of several projects the user means → ask, don't pick.

Rationalizations (all false)

Excuse	Reality
"It's obviously the only project"	Read `projects list` and confirm anyway. Cheap.
"The user clearly wants all of them gone"	Confirm each domain individually. No bulk delete.
"I'll soft-delete / restore the project later"	The project record is hard-deleted with no recovery; historical runs are preserved separately.
"Echo-confirm is just ceremony"	It's the thing that makes a wrong delete impossible.