agentleFS
Catherine1401Catherine1401/agent-skills/skills/user-policy-pj/SKILL.md

user-policy-pj

Skill2 starsChanged 55 days agoMITView on GitHub

Update the current project's own policy file for a project-specific requirement. Use for rules that apply only to this project; not user-level policy (use user-policy), skills, or plugins.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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
  1. Very specific:

    When the file is a symlink into the private projects checkout (~/agent-skills-projects, or AGS_PROJECTS_DIR), edit through the link without …

    line 7
  2. Distinctive:

    Never put secrets or personal data in the file.

    line 10

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
  • Edit only the project's own policy file, in this order: project-root CLAUDE.md, .claude/CLAUDE.md, project-root AGENTS.md; when none exists, create the project-root CLAUDE.md. Never edit shared-rules/user.md, user-level instruction files, or installed policy copies.
  • When the file is a symlink into the private projects checkout (~/agent-skills-projects, or AGS_PROJECTS_DIR), edit through the link without replacing it, and never copy its content into this repo. Committing or pushing that checkout needs the user's approval.
  • Translate the requirement into the fewest actionable rules that change agent decisions. Write them in English, without exception.
  • Preserve unrelated rules and user intent. Remove redundant, generic, or conflicting rules, including rules already covered by user-level policy.
  • Never put secrets or personal data in the file.

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.