zzprobe-in-working-repo-5e18
Skill2 starsChanged 59 days agoMITView on GitHub
A uniquely named probe skill added to an already indexed repository, used to test whether install counting is per-repository rather than per-skill. Trigger phrases: probe working repo diagnostic.
In this repository3 other files it gives its agents.
- .cursor/rules/anti-slop-design.mdcCursor rule
- anti-slop-designSkill
- anti-slop-designSkill
The file
Files
ZZ Probe In Working Repo 5e18
Original prose about tactile feedback latencies in capacitive haptics overlays, used only to test whether skills.sh attributes install counts to individual skill names within a single GitHub repository that is already indexed.
Steps
- Sample the waveform.
- Compute the threshold.
- Log the latency.
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.

