All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Trial Ops Safety Intake Exception Triage QueueUse when the research safety-event intake administration workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the safety-event routing packet with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; events are routed on time without severity, causality, or treatment conclusions being generated. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Trial Ops Safety Intake Recovery Readiness DrillUse when the research safety-event intake administration workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the safety-event routing packet with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; events are routed on time without severity, causality, or treatment conclusions being generated. Use configured search, f...Votes: 0GitHub stars: 2
- Trial Ops Safety Intake Scenario Sensitivity MatrixUse when the research safety-event intake administration team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the safety-event routing packet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; events are routed on time without severity, causality, or treatment conclusions being generated. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Trial Ops Safety Intake Scope Intake GateUse when a new research safety-event intake administration request needs a bounded work scope to produce a scoped intake card for the safety-event routing packet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; events are routed on time without severity, causality, or treatment conclusions being generated. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence,...Votes: 0GitHub stars: 2
- Trial Ops Safety Intake Source Provenance LedgerUse when a decision about research safety-event intake administration depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the safety-event routing packet. Success means each material claim has a source, version/date, location, and confidence note; events are routed on time without severity, causality, or treatment conclusions being generated. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and ...Votes: 0GitHub stars: 2
- Trial Ops Safety Intake Threshold Rule CheckUse when a research safety-event intake administration decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the safety-event routing packet showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; events are routed on time without severity, causality, or treatment conclusions being generated. Use configured s...Votes: 0GitHub stars: 2
- Trial Ops Sample Custody Approval Evidence PacketUse when a research specimen chain-of-custody administration result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the specimen custody reconciliation containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; coded identities reconcile across handoffs and missing custody evidence is escalated without reconst...Votes: 0GitHub stars: 2
- Trial Ops Sample Custody Change Impact TraceUse when a version, rule, source, or stakeholder change may affect research specimen chain-of-custody administration to produce a before/after change record and impact map for the specimen custody reconciliation. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; coded identities reconcile across handoffs and missing custody evidence is escalated without reconstructing a gap. Use configured search, fetch, read, ...Votes: 0GitHub stars: 2
- Trial Ops Sample Custody Closeout Handoff LedgerUse when a research specimen chain-of-custody administration work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the specimen custody reconciliation with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; coded identities reconcile across handoffs and missing custody evidence is escalated without reconstructing a gap. Use conf...Votes: 0GitHub stars: 2
- Trial Ops Sample Custody Completeness ReconciliationUse when the research specimen chain-of-custody administration workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the specimen custody reconciliation with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; coded identities reconcile across handoffs and missing custody evidence is escalated without reconstructing a...Votes: 0GitHub stars: 2
- Trial Ops Sample Custody Exception Triage QueueUse when the research specimen chain-of-custody administration workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the specimen custody reconciliation with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; coded identities reconcile across handoffs and missing custody evidence is escalated without reconstructing a gap. Use con...Votes: 0GitHub stars: 2
- Trial Ops Sample Custody Recovery Readiness DrillUse when the research specimen chain-of-custody administration workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the specimen custody reconciliation with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; coded identities reconcile across handoffs and missing custody evidence is escalated without reconstructing a g...Votes: 0GitHub stars: 2
- Trial Ops Sample Custody Scenario Sensitivity MatrixUse when the research specimen chain-of-custody administration team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the specimen custody reconciliation with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; coded identities reconcile across handoffs and missing custody evidence is escalated without reconstructing a gap. Use configure...Votes: 0GitHub stars: 2
- Trial Ops Sample Custody Scope Intake GateUse when a new research specimen chain-of-custody administration request needs a bounded work scope to produce a scoped intake card for the specimen custody reconciliation. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; coded identities reconcile across handoffs and missing custody evidence is escalated without reconstructing a gap. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and ...Votes: 0GitHub stars: 2
- Trial Ops Sample Custody Source Provenance LedgerUse when a decision about research specimen chain-of-custody administration depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the specimen custody reconciliation. Success means each material claim has a source, version/date, location, and confidence note; coded identities reconcile across handoffs and missing custody evidence is escalated without reconstructing a gap. Use configured search, fetch, read, browser, test, and write capabili...Votes: 0GitHub stars: 2
- Trial Ops Sample Custody Threshold Rule CheckUse when a research specimen chain-of-custody administration decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the specimen custody reconciliation showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; coded identities reconcile across handoffs and missing custody evidence is escalated without reconstruc...Votes: 0GitHub stars: 2
- Trial Ops Site Startup Approval Evidence PacketUse when a clinical-trial site startup coordination result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the site startup tracker containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; each prerequisite has an owner and dated evidence; activation remains an authorized investigator or sponsor decision. Us...Votes: 0GitHub stars: 2
- Trial Ops Site Startup Change Impact TraceUse when a version, rule, source, or stakeholder change may affect clinical-trial site startup coordination to produce a before/after change record and impact map for the site startup tracker. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each prerequisite has an owner and dated evidence; activation remains an authorized investigator or sponsor decision. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Trial Ops Site Startup Closeout Handoff LedgerUse when a clinical-trial site startup coordination work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the site startup tracker with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; each prerequisite has an owner and dated evidence; activation remains an authorized investigator or sponsor decision. Use configured search, fe...Votes: 0GitHub stars: 2
- Trial Ops Site Startup Completeness ReconciliationUse when the clinical-trial site startup coordination workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the site startup tracker with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; each prerequisite has an owner and dated evidence; activation remains an authorized investigator or sponsor decision. Use configu...Votes: 0GitHub stars: 2
- Trial Ops Site Startup Exception Triage QueueUse when the clinical-trial site startup coordination workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the site startup tracker with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; each prerequisite has an owner and dated evidence; activation remains an authorized investigator or sponsor decision. Use configured search, f...Votes: 0GitHub stars: 2
- Trial Ops Site Startup Recovery Readiness DrillUse when the clinical-trial site startup coordination workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the site startup tracker with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; each prerequisite has an owner and dated evidence; activation remains an authorized investigator or sponsor decision. Use configure...Votes: 0GitHub stars: 2
- Trial Ops Site Startup Scenario Sensitivity MatrixUse when the clinical-trial site startup coordination team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the site startup tracker with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each prerequisite has an owner and dated evidence; activation remains an authorized investigator or sponsor decision. Use configured search, fetch, ...Votes: 0GitHub stars: 2
- Trial Ops Site Startup Scope Intake GateUse when a new clinical-trial site startup coordination request needs a bounded work scope to produce a scoped intake card for the site startup tracker. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each prerequisite has an owner and dated evidence; activation remains an authorized investigator or sponsor decision. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Recor...Votes: 0GitHub stars: 2
- Trial Ops Site Startup Source Provenance LedgerUse when a decision about clinical-trial site startup coordination depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the site startup tracker. Success means each material claim has a source, version/date, location, and confidence note; each prerequisite has an owner and dated evidence; activation remains an authorized investigator or sponsor decision. Use configured search, fetch, read, browser, test, and write capabilities only when re...Votes: 0GitHub stars: 2
- Trial Ops Site Startup Threshold Rule CheckUse when a clinical-trial site startup coordination decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the site startup tracker showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; each prerequisite has an owner and dated evidence; activation remains an authorized investigator or sponsor decision. Use c...Votes: 0GitHub stars: 2
- Trial Ops Study Closeout Approval Evidence PacketUse when a clinical research closeout and archive result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the study closeout evidence matrix containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; only verified closeout evidence is marked complete and retention or destruction decisions remain with the record...Votes: 0GitHub stars: 2
- Trial Ops Study Closeout Change Impact TraceUse when a version, rule, source, or stakeholder change may affect clinical research closeout and archive to produce a before/after change record and impact map for the study closeout evidence matrix. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; only verified closeout evidence is marked complete and retention or destruction decisions remain with the record owner. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Trial Ops Study Closeout Completeness ReconciliationUse when the clinical research closeout and archive workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the study closeout evidence matrix with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; only verified closeout evidence is marked complete and retention or destruction decisions remain with the record owner. U...Votes: 0GitHub stars: 2
- Trial Ops Study Closeout Exception Triage QueueUse when the clinical research closeout and archive workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the study closeout evidence matrix with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; only verified closeout evidence is marked complete and retention or destruction decisions remain with the record owner. Use configured...Votes: 0GitHub stars: 2
- Trial Ops Study Closeout Handoff LedgerUse when a clinical research closeout and archive work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the study closeout evidence matrix with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; only verified closeout evidence is marked complete and retention or destruction decisions remain with the record owner. Use configured ...Votes: 0GitHub stars: 2
- Trial Ops Study Closeout Recovery Readiness DrillUse when the clinical research closeout and archive workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the study closeout evidence matrix with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; only verified closeout evidence is marked complete and retention or destruction decisions remain with the record owner. Use...Votes: 0GitHub stars: 2
- Trial Ops Study Closeout Scenario Sensitivity MatrixUse when the clinical research closeout and archive team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the study closeout evidence matrix with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; only verified closeout evidence is marked complete and retention or destruction decisions remain with the record owner. Use configured searc...Votes: 0GitHub stars: 2
- Trial Ops Study Closeout Scope Intake GateUse when a new clinical research closeout and archive request needs a bounded work scope to produce a scoped intake card for the study closeout evidence matrix. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; only verified closeout evidence is marked complete and retention or destruction decisions remain with the record owner. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authori...Votes: 0GitHub stars: 2
- Trial Ops Study Closeout Source Provenance LedgerUse when a decision about clinical research closeout and archive depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the study closeout evidence matrix. Success means each material claim has a source, version/date, location, and confidence note; only verified closeout evidence is marked complete and retention or destruction decisions remain with the record owner. Use configured search, fetch, read, browser, test, and write capabilities on...Votes: 0GitHub stars: 2
- Trial Ops Study Closeout Threshold Rule CheckUse when a clinical research closeout and archive decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the study closeout evidence matrix showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; only verified closeout evidence is marked complete and retention or destruction decisions remain with the record ow...Votes: 0GitHub stars: 2
- Trial Ops Visit Operations Approval Evidence PacketUse when a research visit and schedule coordination result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the visit schedule exception queue containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; the schedule does not disclose unnecessary health details and missed windows are routed to the study team. Use...Votes: 0GitHub stars: 2
- Trial Ops Visit Operations Change Impact TraceUse when a version, rule, source, or stakeholder change may affect research visit and schedule coordination to produce a before/after change record and impact map for the visit schedule exception queue. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the schedule does not disclose unnecessary health details and missed windows are routed to the study team. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2
- Trial Ops Visit Operations Closeout Handoff LedgerUse when a research visit and schedule coordination work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the visit schedule exception queue with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; the schedule does not disclose unnecessary health details and missed windows are routed to the study team. Use configured search, fet...Votes: 0GitHub stars: 2
- Trial Ops Visit Operations Completeness ReconciliationUse when the research visit and schedule coordination workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the visit schedule exception queue with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; the schedule does not disclose unnecessary health details and missed windows are routed to the study team. Use configur...Votes: 0GitHub stars: 2
- Trial Ops Visit Operations Exception Triage QueueUse when the research visit and schedule coordination workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the visit schedule exception queue with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; the schedule does not disclose unnecessary health details and missed windows are routed to the study team. Use configured search, fe...Votes: 0GitHub stars: 2
- Trial Ops Visit Operations Recovery Readiness DrillUse when the research visit and schedule coordination workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the visit schedule exception queue with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; the schedule does not disclose unnecessary health details and missed windows are routed to the study team. Use configured...Votes: 0GitHub stars: 2
- Trial Ops Visit Operations Scenario Sensitivity MatrixUse when the research visit and schedule coordination team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the visit schedule exception queue with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the schedule does not disclose unnecessary health details and missed windows are routed to the study team. Use configured search, fetch, r...Votes: 0GitHub stars: 2
- Trial Ops Visit Operations Scope Intake GateUse when a new research visit and schedule coordination request needs a bounded work scope to produce a scoped intake card for the visit schedule exception queue. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the schedule does not disclose unnecessary health details and missed windows are routed to the study team. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record...Votes: 0GitHub stars: 2
- Trial Ops Visit Operations Source Provenance LedgerUse when a decision about research visit and schedule coordination depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the visit schedule exception queue. Success means each material claim has a source, version/date, location, and confidence note; the schedule does not disclose unnecessary health details and missed windows are routed to the study team. Use configured search, fetch, read, browser, test, and write capabilities only when rel...Votes: 0GitHub stars: 2
- Trial Ops Visit Operations Threshold Rule CheckUse when a research visit and schedule coordination decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the visit schedule exception queue showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; the schedule does not disclose unnecessary health details and missed windows are routed to the study team. Use co...Votes: 0GitHub stars: 2
- Aas Devtools Cli Option Contract Approval Evidence PacketUse when a developer CLI option contracts result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the CLI option contract matrix containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; documented options match executable behavior and invalid combinations fail clearly. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Aas Devtools Cli Option Contract Change Impact TraceUse when a version, rule, source, or stakeholder change may affect developer CLI option contracts to produce a before/after change record and impact map for the CLI option contract matrix. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; documented options match executable behavior and invalid combinations fail clearly. Use configured search, fetch, read, browser, test, and write capabilities only when relevan...Votes: 0GitHub stars: 2
- Aas Devtools Cli Option Contract Closeout Handoff LedgerUse when a developer CLI option contracts work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the CLI option contract matrix with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; documented options match executable behavior and invalid combinations fail clearly. Use configured search, fetch, read, browser, test, and write ca...Votes: 0GitHub stars: 2
- Aas Devtools Cli Option Contract Completeness ReconciliationUse when the developer CLI option contracts workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the CLI option contract matrix with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; documented options match executable behavior and invalid combinations fail clearly. Use configured search, fetch, read, browser, test...Votes: 0GitHub stars: 2