Draft Nda
Skill AktivDraft a detailed Non-Disclosure Agreement between two parties covering information types, jurisdiction, and clauses needing legal review. Use when creating confidentiality agreements or preparing an NDA for a partnership.
Draft a detailed Non-Disclosure Agreement between two parties, ensuring key clauses like information types and jurisdiction are covered, while clearly identifying sections needing legal review.
Funktionen
- Drafts comprehensive NDAs
- Covers information types and jurisdiction
- Marks clauses requiring legal review
- Provides plain-language explanations
- Outputs summary, full document, and customization notes
Anwendungsfälle
- Creating confidentiality agreements for partnerships
- Preparing NDAs for potential business collaborations
- Drafting a starting point for legal agreements
Nicht-Ziele
- Providing legal advice
- Acting as a substitute for a licensed attorney
- Handling complex or highly specialized legal scenarios without attorney input
Trust
- warning:Issues AttentionThere are 8 open issues and 0 closed issues in the last 90 days, indicating slow or no maintainer response to recent issues.
Installation
Zuerst Marketplace hinzufügen
/plugin marketplace add phuryn/pm-skills/plugin install pm-toolkit@pm-skillsQualitätspunktzahl
Vertrauenssignale
Ähnliche Erweiterungen
Master Claude for Legal
100Master-Skill für Rechtsteams, die Claude verwenden. Lädt die richtige Referenz für die Benutzerfrage (Konfiguration von Privilegien, MCP-Härtung, Verifizierung, lange Dokumente, Muster für Fachbereiche, Skill-Erstellung) und leitet an spezialisierte Starter-Skills weiter (NDA-Triage, Versionsvergleich, Besprechungszusammenfassung, Zitationsverifizierung, Status-Synthese). Wird automatisch aufgerufen, wenn der Benutzer juristische Arbeit, Verträge, Redlines, NDAs, Privilegien, Anwaltsgeheimnis, Gerichtsakten, Vernehmungen, regulatorische Compliance erwähnt oder fragt, wie Claude für eine Anwaltskanzlei oder ein internes Rechtsteam eingerichtet wird.
Prepare Inspection Readiness
100Prepare an organisation for regulatory inspection by assessing readiness against agency-specific focus areas (FDA, EMA, MHRA). Covers warning letter and 483 theme analysis, mock inspection protocols, document bundle preparation, inspection logistics, and response template creation. Use when a regulatory inspection has been announced or is anticipated, when a periodic self-assessment is due, when new systems have been implemented since the last inspection, or after a significant audit finding that may attract regulatory attention.
Nda Generator
98Create appropriate non-disclosure agreements for different business contexts with balanced terms and proper scope definitions
Triage Nda
98Rapidly triage an incoming NDA and classify it as GREEN (standard approval), YELLOW (counsel review), or RED (full legal review). Use when a new NDA arrives from sales or business development, when screening for embedded non-solicits, non-competes, or missing carveouts, or when deciding whether an NDA can be signed under standard delegation.
Monitor Data Integrity
100Design and operate a data integrity monitoring programme based on ALCOA+ principles. Covers detective controls, audit trail review schedules, anomaly detection patterns (off-hours activity, sequential modifications, bulk changes), metrics dashboards, investigation triggers, and escalation matrix definition. Use when establishing a data integrity monitoring programme for GxP systems, preparing for inspections where data integrity is a focus area, after a data integrity incident requiring enhanced monitoring, or when implementing MHRA, WHO, or PIC/S guidance.
Investigate Capa Root Cause
100Investigate root causes and manage CAPAs (Corrective and Preventive Actions) for compliance deviations. Covers investigation method selection (5-Why, fishbone, fault tree), structured root cause analysis, corrective vs preventive action design, effectiveness verification, and trend analysis. Use when an audit finding requires a CAPA, when a deviation or incident occurs in a validated system, when a regulatory observation needs a formal response, when a data integrity anomaly requires investigation, or when recurring issues suggest a systemic root cause.