agentleFS
matthewwong525matthewwong525/WongStack/.agents/plugins/access/SKILL.md

access

Skill7 starsChanged 4 days agoMITView on GitHub

See who can sign in and what each person may use; add, change or remove a person.

29 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use calendar and setup.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • jacobraskSkill

    calendar

    Interact with Apple Calendar via AppleScript. Use when the user asks to check calendar, view events, create events, manage schedule, find free time, or list calendars. Triggers include "my calendar", "my schedule", "calendar events", "create event", "add to calendar", "what's on my calendar", "free time", "available slots", "upcoming events", "today's events". Requires macOS with Calendar.app.

    Also in 3 projects that use this

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 28 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read status first. Name each person, their role, apps and key levels in plain words, never as JSON.

    line 34
  2. Distinctive:

    Before each save, say what changes, for whom, and ask.

    line 35
  3. Very specific:

    After a save, read status again and say what is now true.

    line 36

“Common” is measured: kept by at least 6 in 10 of the 28 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/access

You read and change the app's people as the person in the chat. The app decides what they may do: only the owner or an Admin can change people. The Access page owns the rules.

From the repo root, call the app with this computer's sign-in. The app's address is app in .agents/access/slots.json, else the one a WongStack install records:

node --input-type=module -e '
import { appOrigin } from "./.claude/skills/access/scripts/lib/client.mjs";
import { headers, signInHelp } from "./.claude/skills/access/signin/computer.mjs";
const app = appOrigin(".");
const signed = headers(app);
if (!signed) throw new Error(`Not signed in: ${signInHelp(app)}`);
const [, , path, body] = process.argv;
const init = { headers: { ...signed, "content-type": "application/json", ...(body && { origin: app }) }, redirect: "error" };
const answer = await fetch(new URL(`/api/access/${path}`, app), body ? { ...init, method: "POST", body } : init);
console.log(answer.status, await answer.text());' <path> [json]
You wantPathBody
Who has whatstatusnone
Add or change a personpeople{"email":"a@shop.com","removed":false,"apps":{"<app>":true},"keys":{"<key>":"read"}}
Give a person a rolepeople{"email":"a@shop.com","removed":false,"role":"<role id>"}
Remove a personpeople{"email":"a@shop.com","removed":true}
Make or change a roleroles{"name":"Sales","apps":{…},"keys":{…}}, with id to change one
  1. Read status first. Name each person, their role, apps and key levels in plain words, never as JSON.
  2. Before each save, say what changes, for whom, and ask. Save only on a yes, one change at a time.
  3. After a save, read status again and say what is now true.
  4. A refusal is {"code": "<why>"}: tell the person in plain words. owner_required: they are not the owner or an Admin; owner_setup_required: the app names no owner, or the sign-in did not reach it.
  5. With no .agents/access/slots.json, Access is not set up: offer the setup guide.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.