sa
Skill1 starsChanged 6 months agoNo licenceView on GitHub
Use when analyzing requirements before implementation OR auditing security of an existing design/codebase. Two modes — (1) System Analyst — turn fuzzy requests into concrete artifacts: user stories, use cases, acceptance criteria, sequence/flow diagrams, data models (ER), API specs (request/response/error), state transitions, edge-case enumeration; (2) Security Audit — review code, architecture, auth flow, data handling, dependencies, infra config for OWASP top 10, broken auth, IDOR, injection, XSS, SSRF, secret leakage, insecure deserialization, missing rate limiting, weak crypto, unsafe defaults. Trigger on Thai keywords วิเคราะห์ requirement/วิเคราะห์ระบบ/เก็บ requirement/SA/system analyst/use case/user story/flow diagram/sequence diagram/ER diagram/data model/API spec/ออกแบบระบบ/architecture/security/ตรวจ security/audit/ช่องโหว่/auth flow/threat model and English keywords analyze/requirement/spec/use case/user story/acceptance criteria/sequence diagram/flowchart/ERD/data model/API design/threat model/security review/audit/OWASP/vulnerability/IDOR/SSRF/CSRF/XSS/SQLi. Use BEFORE implementing a non-trivial feature (to nail down spec) or AFTER a design/implementation lands (to validate security). Examples "วิเคราะห์ requirement หน้านี้ให้หน่อย", "เขียน use case ของ flow จองคิว", "ออกแบบ data model สำหรับ ticket", "spec API ของ login ให้หน่อย", "ตรวจ security ของ auth middleware", "หา threat ใน flow นี้", "review ช่องโหว่ของหน้า kiosk".
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 9 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.