spec-idea
Skill0 starsChanged 29 days agoMITView on GitHub
Use when someone wants to propose an idea for inite-visibility (the AI-visibility MCP server) or for the inite.ai audit it bridges to, without writing code — turns it into a plain-language spec and files it as an issue in inite-ai/inite-visibility.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- inite-ai/inite-brain-servicetheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- inite-ai/inite-brain-service★ 43same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- contributeSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
If one exists, offer to comment on it instead.
- Distinctive: line 17
Write the issue body with these headings: What do you want to be possible?
- Very specific: line 29
Never paste a token or the contents of ~/.config/inite/mcp.json.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/spec-idea — propose, don't build
Explain in plain words as you go. No code, no branches.
- Restate the idea; ask at most 3 clarifying questions.
- Say which part it touches: a local check (runs on the user's machine, facts only), the bridge/sign-in, or the inite.ai audit/score/Atlas (server-side — still filed here, and labelled as such).
- Search first:
gh issue list -R inite-ai/inite-visibility --search "<key words>" --state all. If one exists, offer to comment on it instead. - Write the issue body with these headings: What do you want to be possible? · Who is it for / why · How would you know it works? (a site to try it on and the expected report) · Spec (problem, what the tool reports, tool surface change, what is fetched, risks, out of scope, zone from AGENTS.md).
- Show it, get a yes, then file:
gh issue create -R inite-ai/inite-visibility --title "idea: <title>" --label idea --body-file <file>. Withoutgh, give the personhttps://github.com/inite-ai/inite-visibility/issues/new?template=product-idea.ymland the text to paste. - Share the issue link and what happens next (a maintainer reviews it).
Never paste a token or the contents of ~/.config/inite/mcp.json.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

