payments
Skill0 starsChanged 18 days agoMITView on GitHub
Review or record reported partial/full payments for issued Otis invoices.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- whawkinsiv/solo-founder-skillstheir own version, first seen Oct 25, 2026
- whawkinsiv/claude-code-skillstheir own version, first seen Oct 17, 2026
- vietnamtrainingpilot-oss/ateliertheir own version, first seen Oct 17, 2026
- MartinOlivero/saas-buildertheir own version, first seen Oct 13, 2026
- openai/pluginstheir own version, first seen Oct 13, 2026
- jholhewres/devclaw-skillstheir own version, first seen Oct 9, 2026
Used with
Projects with it also use journey, integrations and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MeshJSSkilljourney
Create session learning logs that persist institutional memory across Claude Code sessions.
Also in 4 projects that use this
rohinipachantaSkillintegrations
Use when connecting Claude to external apps (Slack, GitHub, Gmail, etc.) using the Composio Connect framework.
Also in 3 projects that use this
nicolas-webdevSkilllanding-page
Architecture and copywriting framework for high-converting landing pages. Use when building landing pages, sales pages, product pages, or lead capture pages. Follows a proven 8-section structure optimized for conversions.
Also in 3 projects that use this
nilssonrSkillseo
Full SEO workflow for auditing pages and creating SEO-optimized content. Provides checklists with educational explanations aligned with Google Search Central documentation.
Also in 3 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- openai/plugins★ 7.8ksame name
- butterbase-ai/butterbase-plugin★ 535same name
- butterbase-ai/butterbase-skills★ 535same name
- whawkinsiv/solo-founder-skills★ 260same name
- whawkinsiv/claude-code-skills★ 258same name
- jholhewres/devclaw-skills★ 4same name
- MartinOlivero/saas-builder★ 4same name
- leonardoaraujosantos/my_ai_skills★ 1same name
- vietnamtrainingpilot-oss/atelier★ 1same name
- muxammadmamajonov/dot-claude★ 0same 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 repository9 other files it gives its agents.
- add-expenseSkill
- business-settingsSkill
- clientsSkill
- create-invoiceSkill
- exportSkill
- invoicesSkill
- menuSkill
- record-workSkill
- tax-settingsSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
2
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
- Distinctive: line 8
Use the connected Otis MCP at https://mcp.otisbase.com/mcp.
- Distinctive: line 10
Read otis://docs/workflows when available.
“Common” is measured: kept by at least 6 in 10 of the 9 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.
Files
Payments with Otis
Use the connected Otis MCP at https://mcp.otisbase.com/mcp. If its tools are unavailable, explain connection and email-code sign-in in the browser; never ask for codes in chat or simulate a successful action. First find the business with businesses_list and pass its business_id on scoped calls. Read business_get for missing setup. Read otis://docs/workflows when available. Ask only for missing facts. Never invent prices, payments, tax treatment or consent. Monetary values use integer currency minor units. Reuse a stable request_id for identical write retries; follow structured blockers instead of guessing. Workflow tools: invoices_list, invoice_get, payments_list, payment_record.
- Clarify whether the user wants to review payments or record one. Read the relevant invoice and payments; paginate results. These are reported facts, not verified bank activity.
- Before payment_record, establish the issued invoice, actual received amount/date and stable business-wide reference. Reuse that reference for the same payment. Resolve mismatches or overpayments rather than splitting them to hide a conflict. Payment reversals and unapplied credits are unavailable. Return the recorded payment and updated invoice balance.
Stay within the requested workflow. A command starts guided work; it does not approve unspecified writes or invoice issuance. Show the recorded result and any remaining steps.
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.