agentleFS
Sign inStart free
latour-ailatour-ai/skills/pe-nda-review/SKILL.md

pe-nda-review

Skill69 starsChanged 27 days agoNo licenceView on GitHub

Review an inbound NDA or confidentiality agreement from the buy-side perspective and produce a severity-ranked issue memo with suggested markup language — non-solicit scope and duration, standstills, affiliate and portfolio company attribution, term length, definition breadth, residuals, employee and customer contact restrictions, financing tree exclusivity, and return-or-destroy obligations — ending in a sign-as-is / sign-with-markups / send-to-counsel call. For private equity, growth equity, credit, and corporate development teams turning routine process NDAs; associates, VPs, and in-house counsel. Trigger on phrases like "review this NDA," "can we sign this," "check this confi," "what's wrong with this NDA," "mark up this confidentiality agreement," "is this standstill a problem," "banker sent an NDA," or when a user uploads an NDA, confidentiality agreement, or CA from a sell-side process. Do NOT use for a hedge fund side letter — use the side-letter-term-extractor skill. Do NOT use for a credit agreement — use the credit-agreement-covenant-extractor skill. This is a commercial screen, not legal advice.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free