Research Trade Secret Protections For Departing Employee
ASecurity
Analyzing trade secret and restrictive covenant enforcement options following a departing employee scenario, using employment agreements, a forensic report, and exit documentation.
Installs into .claude/skills of the current project.
Are you the author of Research Trade Secret Protections For Departing Employee?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/sunyifeisb-art-research-trade-secret-protections-for-departing-em)
---
name: research-trade-secret-protections-departing-employee
task_id: intellectual-property/research-trade-secret-protections-for-departing-employee
description: Analyzing trade secret and restrictive covenant enforcement options following a departing employee scenario, using employment agreements, a forensic report, and exit documentation.
activates_for: [planner, solver, checker]
---
# Skill: Research Trade Secret Protections for Departing Employee
## 1. Subject-matter triage
- Identify the governing jurisdiction for each agreement, claim, and requested remedy before analyzing enforceability.
- Separate the analysis by document and by theory: trade secret status, misappropriation, restrictive covenants, access-based claims, and emergency relief.
- If multiple agreements, systems, or categories of information are in play, enumerate them first and analyze each on its own record rather than collapsing them into one pass.
- Treat the forensic report, exit materials, and internal communications as distinct evidence streams; map each to the element it supports or undermines.
## 2. Failure modes the skill is correcting
- Analyzing restrictive covenants without first determining whether the governing law permits the restriction and under what limits.
- Treating a forensic artifact as proof of misappropriation without tying it to a legal element, a protected information category, or a duty breached.
- Assuming information is a trade secret without testing secrecy, economic value, and the employer’s reasonable protective measures.
- Overlooking separation paperwork, return certifications, device/account controls, or post-exit communications that may support or weaken enforcement.
- Stating remedies in the abstract without connecting them to the factual predicates and the applicable legal standard.
- Reaching conclusions without naming the controlling authority that supports the proposition.
## 3. Legal frameworks / domain conventions that apply
- Trade secret claims generally require a protected information category, reasonable measures to maintain secrecy, and acquisition, disclosure, or use through improper means or breach of a duty of confidence.
- Use the governing statute and section for the relevant trade secret regime, together with any leading case law on secrecy, reasonable measures, improper means, and available remedies.
- Assess reasonable measures by looking at actual controls: need-to-know access, confidentiality obligations, labeling, technical restrictions, exit controls, training, and enforcement history.
- Restrictive covenant enforceability is jurisdiction-specific; analyze the specific covenant, the legitimate business interest asserted, and whether scope, duration, geography, and activity limits are reasonable under the governing law.
- If the source materials invoke emergency relief, assess any statutory ex parte seizure or comparable extraordinary remedy using the exact statutory standard before recommending it.
- If the governing jurisdiction recognizes inevitable disclosure, analyze the doctrine as a remedy-specific theory and confirm whether the requested relief fits the jurisdiction’s law.
- Access-based statutes, computer misuse statutes, and breach-of-duty theories may supplement trade secret claims when authorized access was exceeded or retained data was not properly returned.
- Remedies should be analyzed separately: injunction, preservation orders, damages, enhanced damages where authorized, fees where authorized, and any special seizure or forensic preservation relief.
- Cite each controlling authority by name and section, rule, or leading case for every legal proposition relied upon.
## 4. Analytical scaffolds
1. Build a document map.
- List each agreement, exit document, forensic artifact, and relevant communication set.
- For each item, note governing law, parties covered, operative obligations, and any express confidentiality or post-employment restriction.
2. Analyze trade secret status.
- Identify the information categories at risk.
- Test each category against secrecy, economic value, and the employer’s protective measures.
- Tie every cited protection measure to the specific record evidence and to the legal standard.
3. Analyze misappropriation.
- For each forensic finding, ask whether it shows possession, access, transfer, retention, disclosure, or use.
- Connect each finding to a specific theory: acquisition by improper means, disclosure in breach of duty, or use without consent.
- Distinguish suspicious conduct from conduct that satisfies the legal elements.
4. Analyze restrictive covenants agreement by agreement.
- State the covenant type, the scope of restricted activity, duration, geography, and any stated business-interest justification.
- Assess enforceability under the governing jurisdiction and identify any blue-pencil, reformation, or statutory limits if recognized.
- Compare the covenant’s language to the employee’s role and the risk profile described in the documents.
5. Review exit and return materials.
- Compare representations about returned devices, files, credentials, and retained copies against forensic findings.
- Identify any inconsistencies, omissions, or preservation issues that affect credibility or remedies.
6. Review the employer’s response record.
- Identify delay, waiver, inconsistency, or overreach risks in the response, including any facts that may weaken injunctive relief.
7. Assess remedies and relief strategy.
- Link each requested remedy to the underlying cause of action and the governing authority.
- Separate ordinary injunctive relief from extraordinary relief and state the threshold for each.
8. Convert each issue into a client-impact assessment.
- State the legal significance, the practical consequence, and the next factual question needed to close the gap.
- When relevant, include the scale of the issue using figures or time periods from the source record, and cross-reference any related document or clause that changes the analysis.
## 5. Vertical / structural / temporal relationships
- Track the chronology: onboarding, access grants, policy acknowledgments, pre-departure activity, exit date, post-exit conduct, and remediation steps.
- Compare obligations across the employment agreement, confidentiality agreement, policies, exit certifications, and any device or data-use terms.
- Identify whether later documents narrow, reinforce, or supersede earlier restrictions or remedies.
- If more than one employee, system, or information set is implicated, state the relationship among them before evaluating liability or relief.
## 6. Output structure conventions
- Write the memo as a legal advisory memo, not as a checklist or raw notes.
- Use conventional sections in a practical sequence: executive summary; documents reviewed; trade secret status; misappropriation; restrictive covenant enforceability; additional claims; remedies and litigation posture; risks and open questions; recommended next steps.
- For each claim or remedy, include: the controlling authority, the elements, the supporting evidence, the weak points, and the litigation or operational consequence.
- Keep the analysis document-specific: separate treatment for each agreement and each major evidence source.
- End with a distinct Recommended Actions block that assigns each action to a responsible role and a timing anchor drawn from the record or, if none exists, a prompt relative deadline tied to the enforcement decision.
- Do not present conclusions without the supporting rule; do not state a remedy without stating the legal basis and the factual predicate.