BusinessLogic
Skill2 starsChanged 44 days agoMITView on GitHub
Model the application as states, transitions, actors and invariants before testing. High-value workflows include account recovery, invitations, approvals, checkout, credits and ownership transfer. Report an observed invariant violation with state evidence. If state cannot be read safely, retain the idea as an unverified lead.
In this repository8 other files it gives its agents.
- bug-bountySkill
- APIAssessmentSkill
- bb-methodologySkill
- EvidenceValidationSkill
- HuntPlanningSkill
- PromptInjectionSkill
- ReconSkill
- WebAssessmentSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 5
Write the invariant in plain language, such as "a user may redeem this benefit once" or "only an owner may approve this transfer".
≈ “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.
Files
Business Logic
Model the application as states, transitions, actors and invariants before testing. High-value workflows include account recovery, invitations, approvals, checkout, credits and ownership transfer.
- Write the invariant in plain language, such as "a user may redeem this benefit once" or "only an owner may approve this transfer".
- Identify the smallest sequence of authorized actions that reaches the decision point. Capture the state before each action.
- Compare roles, workflow order, duplicate submission and stale state using controlled fixtures. Keep concurrency low and bound retries.
- For race hypotheses, require an operator-owned test object, a known safe outcome and a cleanup path. Do not run concurrent writes on production records without that contract.
- Measure the final server-side state, not merely an HTTP status or UI message. Repeat the observation independently and include a negative control.
Report an observed invariant violation with state evidence. If state cannot be read safely, retain the idea as an unverified lead.
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.