discovery-eyes

GitHub

模拟诉讼取证视角,分析团队沟通记录以识别法律风险。通过高亮展示、模式总结及合规重写建议,进行预防性培训,强调诚实与沟通规范,严禁协助隐瞒或销毁证据。

plugins/pm-simulators/skills/discovery-eyes/SKILL.md mohitagw15856/pm-claude-skills

Trigger Scenarios

如何让我们的 Slack 在取证中看起来更合规 训练团队的沟通卫生 像原告律师一样审查此线程 哪些内容不应写入文字

Install

npx skills add mohitagw15856/pm-claude-skills --skill discovery-eyes -g -y
More Options

Non-standard path

npx skills add https://github.com/mohitagw15856/pm-claude-skills/tree/main/plugins/pm-simulators/skills/discovery-eyes -g -y

Use without installing

npx skills use mohitagw15856/pm-claude-skills@discovery-eyes

指定 Agent (Claude Code)

npx skills add mohitagw15856/pm-claude-skills --skill discovery-eyes -a claude-code -g -y

安装 repo 全部 skill

npx skills add mohitagw15856/pm-claude-skills --all -g -y

预览 repo 内 skill

npx skills add mohitagw15856/pm-claude-skills --list

SKILL.md

Frontmatter
{
    "name": "discovery-eyes",
    "description": "Read your team's messages the way opposing counsel would in litigation discovery — prevention training that makes communication hygiene visceral. Use when asked how would our Slack look in discovery, train my team on communication hygiene, review this thread like a plaintiff's lawyer, or what shouldn't we put in writing. Produces the highlighted-exhibit reading of sample messages, the patterns that create legal risk, and a debrief with the write-it-this-way rules — strictly for prevention, never for concealment."
}

Discovery Eyes Skill

Every message your team writes is a potential exhibit with a highlighter across it, read aloud years later, stripped of tone and context. This skill performs that reading on sample messages — jokes that become admissions, speculation that becomes knowledge, "delete this after reading" that becomes the whole case — as prevention training. Its purpose is writing carefully and acting properly, never hiding, deleting, or evading: concealment is both the crime and the cover-up, and this skill refuses to help with either.

What This Skill Produces

  • The exhibit reading — supplied sample messages, highlighted and characterized as a plaintiff's lawyer would
  • The pattern list — the recurring habits that manufacture legal risk out of ordinary work
  • The debrief — write-it-this-way rules that keep candor AND hygiene, plus when-to-pick-up-the-phone guidance

Required Inputs

Ask for these if not provided:

  • Sample messages/threads — real (sanitized) or representative of the team's style
  • The context — industry and the risk surfaces that matter (employment, IP, competition, safety, securities)
  • The audience — engineers, sales, execs — the patterns differ by tribe

Framework: How the Highlighter Reads

  1. Tone strips off: sarcasm, hyperbole, and dark jokes read literally ("this feature will literally kill someone 😂" reads exactly as written, without the emoji's protection).
  2. Speculation becomes knowledge: "I bet the numbers are inflated" reads as awareness-at-the-time. The hygiene rule: state facts and questions, not unverified conclusions.
  3. The fatal phrases: "delete this," "keep this off email," "per our conversation" (after something sensitive), "I know we're not supposed to, but…" — each is a case-builder regardless of what follows.
  4. Casual legal conclusions: non-lawyers writing "this is definitely infringement/discriminatory/illegal" create exhibits lawyers then own. Rule: describe behavior, route legal characterization to counsel.
  5. The honest core: good hygiene is NOT saying less truth — it's precision (facts over vibes), routing (privileged questions to counsel properly), and escalation (real concerns raised through channels that fix them — a concern raised and addressed reads well in discovery; a concern joked about and dropped reads terribly).

Output Format

Exhibit Reading: [team/context]

Prevention training — a plausible adversarial reading of sample messages. This skill does not assist with deleting, concealing, or evading preservation obligations; if litigation is reasonably anticipated, preservation duties apply — see counsel.

The Exhibits

[message, quoted] Highlighted as: [how it reads in a filing] · The pattern: [which habit produced it]

The Pattern List

[The 4–6 recurring habits in these samples, each with its risk mechanism]

Debrief — write it this way

Instead of Write Why
[Plus: the pick-up-the-phone list (what belongs in synchronous conversation — decisions still get documented properly afterward), and the escalate-properly note: raised-and-fixed is the best exhibit there is]

Quality Checks

  • Every reading traces to a supplied message — no invented exhibits
  • The prevention-not-concealment banner appears in the artifact
  • Rewrites preserve the truth content — hygiene is precision, not omission
  • Legal-conclusion language is routed to counsel, not softened into nothing
  • The raised-and-fixed principle appears — the goal is better conduct, not quieter records

Anti-Patterns

  • Do not advise deleting, auto-expiring, or moving topics off-channel to evade records — that request ends the exercise and goes to counsel
  • Do not train people to stop reporting problems — suppressed concerns are worse in court AND in reality
  • Do not sanitize into meaninglessness — a team afraid to write anything ships nothing
  • Do not perform legal analysis — this is communication training; law belongs to lawyers
  • Do not read real named individuals' messages punitively — samples train teams; this is not a surveillance tool

Version History

  • 54fad50 Current 2026-07-19 13:11

Same Skill Collection

exports/openclaw/360-feedback-template/SKILL.md
exports/openclaw/401k-plan-decoder/SKILL.md
exports/openclaw/ab-test-planner/SKILL.md
exports/openclaw/ab-test-readout/SKILL.md
exports/openclaw/accessibility-audit/SKILL.md
exports/openclaw/account-plan/SKILL.md
exports/openclaw/acquirer-red-team/SKILL.md
exports/openclaw/ad-copy/SKILL.md
exports/openclaw/aeo-optimizer/SKILL.md
exports/openclaw/agenda-or-cancel/SKILL.md
exports/openclaw/agent-design-review/SKILL.md
exports/openclaw/agent-observability-spec/SKILL.md
exports/openclaw/agent-spec/SKILL.md
exports/openclaw/ai-ethics-review/SKILL.md
exports/openclaw/ai-eval-plan/SKILL.md
exports/openclaw/ai-feature-prd/SKILL.md
exports/openclaw/ai-product-canvas/SKILL.md
exports/openclaw/air-quality/SKILL.md
exports/openclaw/altitude-shifter/SKILL.md
exports/openclaw/ambiguity-resolver/SKILL.md
exports/openclaw/analyst-relations-brief/SKILL.md
exports/openclaw/announcement-card/SKILL.md
exports/openclaw/api-docs-writer/SKILL.md
exports/openclaw/api-test-plan/SKILL.md
exports/openclaw/api-versioning-strategy/SKILL.md
exports/openclaw/apology-letter/SKILL.md
exports/openclaw/architecture-decision-record/SKILL.md
exports/openclaw/architecture-diagram/SKILL.md
exports/openclaw/archive-strategy/SKILL.md
exports/openclaw/assumption-bounty/SKILL.md
exports/openclaw/assumption-mapper/SKILL.md
exports/openclaw/async-update-format/SKILL.md
exports/openclaw/auto-repair-estimate-decoder/SKILL.md
exports/openclaw/autopilot-charter/SKILL.md
exports/openclaw/benefits-decoder/SKILL.md
exports/openclaw/bid-tender-review/SKILL.md
exports/openclaw/board-deck-narrative/SKILL.md
exports/openclaw/board-minutes/SKILL.md
exports/openclaw/board-pre-read/SKILL.md
exports/openclaw/bom-cost-review/SKILL.md
exports/openclaw/bookkeeping-categorization/SKILL.md
exports/openclaw/boolean-search-builder/SKILL.md
exports/openclaw/brag-doc/SKILL.md
exports/openclaw/brainstorming/SKILL.md
exports/openclaw/brief-builder/SKILL.md
exports/openclaw/briefing-note/SKILL.md
exports/openclaw/budget-builder/SKILL.md
exports/openclaw/budget-variance-analysis/SKILL.md
exports/openclaw/bug-diagnosis/SKILL.md
exports/openclaw/bug-report/SKILL.md

Metadata

Files
0
Version
471c606
Hash
19e9beb3
Indexed
2026-07-19 13:11

- 위키
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-07-30 23:11
浙ICP备14020137号-1 $방문자$