agentleFS
int2t05int2t05/engineering-skills/skills/04-develop/auth-implementation/SKILL.md

auth-implementation

Skill3 starsChanged 28 days agoMITView on GitHub

Implement authentication and authorization with supported mechanisms. Triggers on "implement auth", "实现认证".

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Test real allowed and denied paths, expiration, revocation and cross-user access in an isolated environment.

    line 22

“Common” is measured: kept by at least 6 in 10 of the 4 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

Auth Implementation

When to use

  • Implement authentication and authorization with supported mechanisms.

Not for: security-review for auditing existing security.

Steps

  1. Identify actors, trust boundaries, session lifecycle and provider; check current official guidance.
  2. Implement the chosen flow, secure credential handling, expiration and revocation without custom cryptography.
  3. Enforce server-side ownership and tenant authorization, including login, logout and session renewal behavior.
  4. Test real allowed and denied paths, expiration, revocation and cross-user access in an isolated environment.

Verify

  • Tests cover authentication and object authorization; sessions use supported mechanisms and no secrets leak.

References

  • engineering-principles.md — shared decision boundaries, scope and verification.
  • references/token-patterns.md — session-vs-token decision matrix, JWT structure, refresh-token rotation + reuse detection, revocation strategies
  • references/oauth-flows.md — Authorization Code + PKCE, Client Credentials, Implicit deprecation, Token Exchange (RFC 8693)

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.