malekokour/clinpharm-pmx-skills / skills/build-work-context
build-work-context
VerifiedBuilds, updates, refreshes, and exports portable work context for pharmaceutical and biotech professionals. Use this skill whenever someone wants AI to understand their pharma role, department, responsibilities, projects, sources, terminology, constraints, approval rules, or preferred deliverables; asks to be interviewed; mentions a work profile, professional constitution, project instructions, reusable context, Copilot or ChatGPT context, or wants to combine an existing context file with new project documents. Produces a professional context, project capsule, working pack, and change summary without inventing facts. Do not use for patient-specific clinical decisions or as a substitute for qualified scientific, regulatory, or medical judgment.
| File | Kind | Size |
|---|---|---|
| PASTE.md | markdown | 8.2 KB |
| README.md | markdown | 936 B |
| SKILL.md | skill md | 8.4 KB |
| assets/AI-Working-Pack.template.md | markdown | 774 B |
| assets/Context-Change-Summary.template.md | markdown | 494 B |
| assets/My-Pharma-Work-Context.template.md | markdown | 1.7 KB |
| assets/Project-Context.template.md | markdown | 808 B |
| references/context-contract.md | markdown | 3.8 KB |
| references/department-prompts.md | markdown | 3.3 KB |
| references/evidence-hierarchy.md | markdown | 2.7 KB |
| references/human-review.md | markdown | 2.4 KB |
| references/interview-and-modes.md | markdown | 3.8 KB |
| references/output-states.md | markdown | 2.5 KB |
| references/safety-and-evidence.md | markdown | 3.0 KB |
| references/source-preflight.md | markdown | 2.8 KB |
| scripts/context_validation.pyexecutable | script | 6.4 KB |
| scripts/findings.py | script | 4.7 KB |
| scripts/validate_context.pyexecutable | script | 1.7 KB |
scripts/findings.py
View on GitHub"""VENDORED at build time from shared/scripts/ — do not edit here.
Edit the canonical source and rebuild; a freshness check compares them.
The finding and report contract shared by every deterministic checker.
Two invariants hold across all tools in this repository, and both are enforced
here rather than left to each script:
1. Every finding is **mechanical**. A tool reports that two documents disagree,
that a required item is absent, or that an arithmetic relation does not hold.
It never decides which value is correct, whether a difference matters
clinically, or what dose to give.
2. Every summary states its **denominator**. "3 findings" is not interpretable;
"3 findings across 47 statements checked" is. A report that cannot say what
it examined cannot distinguish a clean document from an unread one.
Author: Malek Okour
Dependencies: Python standard library only — tools must run from a package ZIP
with nothing installed.
"""
from __future__ import annotations
import json
from dataclasses import dataclass, field
SEVERITIES = ("Critical", "Major", "Minor")
@dataclass
class Finding:
"""A mechanical finding. Never a scientific conclusion."""
rule: str
severity: str
item: str
observed: str
expected: str
locator: str
detail: str
kind: str = "mechanical"
def __post_init__(self) -> None:
if self.severity not in SEVERITIES:
raise ValueError(f"severity must be one of {SEVERITIES}, got {self.severity!r}")
def as_dict(self) -> dict[str, str]:
return {
"rule": self.rule,
"severity": self.severity,
"item": self.item,
"observed": self.observed,
"expected": self.expected,
"locator": self.locator,
"detail": self.detail,
"kind": self.kind,
}
@dataclass
class Report:
"""Findings plus the denominators that make a count interpretable."""
tool: str
findings: list[Finding] = field(default_factory=list)
counts: dict[str, int] = field(default_factory=dict)
unassessable: list[dict[str, str]] = field(default_factory=list)
def add(self, finding: Finding) -> None:
self.findings.append(finding)
def cannot_assess(self, item: str, why: str, resolved_by: str) -> None:
"""Record what could not be checked, and what would make it checkable.
Silence about an unexamined item is indistinguishable from a pass, which
is the failure this whole repository is built to avoid.
"""
self.unassessable.append({"item": item, "why": why, "resolved_by": resolved_by})
def count(self, name: str, value: int) -> None:
self.counts[name] = value
def tally(self) -> dict[str, int]:
out = {s: 0 for s in SEVERITIES}
for f in self.findings:
out[f.severity] += 1
return out
def summary(self) -> str:
if not self.counts:
raise ValueError(
f"{self.tool}: refusing to summarise without a denominator. "
"Call count() with what was actually examined."
)
denom = " · ".join(f"{k} {v}" for k, v in sorted(self.counts.items()))
t = self.tally()
return (
f"{self.tool}: {len(self.findings)} finding(s) "
f"[Critical {t['Critical']} · Major {t['Major']} · Minor {t['Minor']}] "
f"across {denom}; {len(self.unassessable)} not assessable"
)
def as_dict(self) -> dict[str, object]:
return {
"tool": self.tool,
"counts": self.counts,
"tally": self.tally(),
"findings": [f.as_dict() for f in self.findings],
"unassessable": self.unassessable,
"boundary": (
"Mechanical findings only. This tool does not decide which value "
"is correct, whether a difference is clinically meaningful, or "
"what dose to give."
),
}
def render(self, as_json: bool = False) -> str:
if as_json:
return json.dumps(self.as_dict(), indent=2)
lines = [self.summary()]
for f in self.findings:
lines.append(f" [{f.severity}] {f.rule}")
lines.append(f" item : {f.item}")
lines.append(f" as written: {f.observed} @ {f.locator}")
if f.expected:
lines.append(f" expected : {f.expected}")
if f.detail:
lines.append(f" detail : {f.detail}")
for u in self.unassessable:
lines.append(f" [CANNOT_ASSESS] {u['item']} — {u['why']}")
lines.append(f" would resolve: {u['resolved_by']}")
return "\n".join(lines)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |