business-operations
Skill0 starsChanged 43 days agoApache-2.0View on GitHub
Coordinate source-grounded business planning, operations, legal and finance drafts with explicit company scope, specialist review, real calculations and authorized actions. Use for business tasks or project business requirements.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Agile-V/agile_v_skillstheir own version, first seen May 25, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Agile-V/agile_v_skills★ 54same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- capability-managerSkill
- decision-routingSkill
- global-orchestratorSkill
- integration-builderSkill
- plugin-safety-reviewSkill
- project-designSkill
- project-discoverySkill
- project-documentationSkill
- project-evidence-reviewSkill
- project-knowledgeSkill
- project-qaSkill
- project-releaseSkill
- project-securitySkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 8
Use the current coordinator and actual available tools.
- Distinctive: line 25
Keep a compact action ledger under docs/ with owner, source references, assumptions, state, review outcome and next step.
- Distinctive: line 35
Use actual calculation tools or deterministic project code for numerical results.
≈ “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 operations
Use the current coordinator and actual available tools. Read references/business-workflows.md before a business assignment. Adapt to the confirmed business and jurisdiction; do not assume USD, legal rules, financial targets, client identity or permission to contact anyone.
Discover the company/project, intended recipient and decision, jurisdiction/date, currency/time period, approved records and permitted actions. Ask focused questions for material gaps before dependent work. Consolidate specialists' questions through the coordinator. Inspect current primary sources for legal/financial claims.
Decompose into research, evidence collection, analysis/calculation, draft, independent review, corrections and an authorized action where requested. Use the optional business_analyst profile for analysis; native scoped fallback roles work too. Legal/finance review needs relevant expertise and current evidence; a role name alone does not establish professional qualification. High-stakes recommendations stay drafts when material evidence or specialist review is missing.
Keep a compact action ledger under docs/ with owner, source references, assumptions, state, review outcome and next step. Draft artifacts carry a clear draft status. Review failures remain visible and block dependent finalization. Never label a generated draft as sent, signed, approved, paid or filed without actual tool evidence.
Carry company/client scope into every retrieval and mutation using runtime-enforced identity and access checks. A knowledge index or prompt containing a company name does not supply authorization. Use project-knowledge only for an approved corpus; retain confirmed facts with source, timestamp, scope and correction/deletion controls.
Use actual calculation tools or deterministic project code for numerical results; validate currency, units, decimal precision, finite output and assumptions. Challenge duplicate operations, stale records and conflicts. Inspect outputs and rerun affected checks after corrections. Follow existing session authorization: drafting or broad business support does not itself authorize payments, signatures, submissions, account changes, public publishing or external messages. Prepare a concrete artifact before requesting any missing action authority.
This skill supplies a workflow, not a business backend, bank connection, legal service or persistent scheduler. Use native orchestration and selected connected tools; do not invent an integration or automatically send business records to external agents.
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.