deal-filer
Skill0 starsChanged 4 months agoNo licenceView on GitHub
File the artifacts a work session produced into the right client deal folder and update the deal index — so every deal stays self-contained instead of leaving models, memos, and transcripts loose in the Cowork/outputs folder. ALWAYS use this skill when Farhan says "file this to the deal", "save these to [company]'s folder", "put this in the deal file", "log this to the deal", "update the deal index", or at session close when a deliverable was produced for a named client (proposal, pricing model, one-pager, transcript). Also trigger when files exist only in the outputs folder and need to land in the deal's folder under `30-deals/`. Folder-per-deal, frontmatter kept in sync with the body, and a row in the pipeline index.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- bulk-cold-emailSkill
- business-doc-updateSkill
- call-prepSkill
- childrens-story-builderSkill
- ci-pricing-job-scraperSkill
- client-safe-deliverableSkill
- coaching-call-updateSkill
- cold-emailSkill
- humanizerSkill
- leverage-finderSkill
- linkedin-post-generatorSkill
- load-f13i-docsSkill
- netlify-deploySkill
- outbound-syncSkill
- pricing-calculator-builderSkill
- pricing-proposal-builderSkill
- pricingsaas-report-builderSkill
- skill-auditorSkill
- website-advisorSkill
- weekly-brain-syncSkill
- weekly-system-reviewSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
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.