All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Omics Data Contrast Design Closeout Handoff LedgerUse when a RNA-sequencing contrast design work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the contrast and covariate review 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 contrast is estimable under the recorded design or the limitation is explicit. Use configured search, fetch, read, browser, test, and write ...Votes: 0GitHub stars: 2
- Omics Data Contrast Design Completeness ReconciliationUse when the RNA-sequencing contrast design workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the contrast and covariate review 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 contrast is estimable under the recorded design or the limitation is explicit. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Omics Data Contrast Design Exception Triage QueueUse when the RNA-sequencing contrast design workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the contrast and covariate review 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 contrast is estimable under the recorded design or the limitation is explicit. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Omics Data Contrast Design Recovery Readiness DrillUse when the RNA-sequencing contrast design workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the contrast and covariate review 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 contrast is estimable under the recorded design or the limitation is explicit. Use configured search, fetch, read, browser, test...Votes: 0GitHub stars: 2
- Omics Data Contrast Design Scenario Sensitivity MatrixUse when the RNA-sequencing contrast design team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the contrast and covariate review with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the contrast is estimable under the recorded design or the limitation is explicit. Use configured search, fetch, read, browser, test, and write capab...Votes: 0GitHub stars: 2
- Omics Data Contrast Design Scope Intake GateUse when a new RNA-sequencing contrast design request needs a bounded work scope to produce a scoped intake card for the contrast and covariate review. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the contrast is estimable under the recorded design or the limitation is explicit. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to thre...Votes: 0GitHub stars: 2
- Omics Data Contrast Design Source Provenance LedgerUse when a decision about RNA-sequencing contrast design depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the contrast and covariate review. Success means each material claim has a source, version/date, location, and confidence note; the contrast is estimable under the recorded design or the limitation is explicit. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record eviden...Votes: 0GitHub stars: 2
- Omics Data Contrast Design Threshold Rule CheckUse when a RNA-sequencing contrast design decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the contrast and covariate review 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 contrast is estimable under the recorded design or the limitation is explicit. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Omics Data Deposit Package Approval Evidence PacketUse when a omics public-deposition package readiness result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the deposition completeness manifest 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; required files and metadata reconcile without disclosing restricted information. Use configured search, fet...Votes: 0GitHub stars: 2
- Omics Data Deposit Package Change Impact TraceUse when a version, rule, source, or stakeholder change may affect omics public-deposition package readiness to produce a before/after change record and impact map for the deposition completeness manifest. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; required files and metadata reconcile without disclosing restricted information. Use configured search, fetch, read, browser, test, and write capabilities onl...Votes: 0GitHub stars: 2
- Omics Data Deposit Package Closeout Handoff LedgerUse when a omics public-deposition package readiness work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the deposition completeness manifest 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; required files and metadata reconcile without disclosing restricted information. Use configured search, fetch, read, browser, test...Votes: 0GitHub stars: 2
- Omics Data Deposit Package Completeness ReconciliationUse when the omics public-deposition package readiness workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the deposition completeness manifest 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; required files and metadata reconcile without disclosing restricted information. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Omics Data Deposit Package Exception Triage QueueUse when the omics public-deposition package readiness workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the deposition completeness manifest 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; required files and metadata reconcile without disclosing restricted information. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Omics Data Deposit Package Recovery Readiness DrillUse when the omics public-deposition package readiness workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the deposition completeness manifest 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; required files and metadata reconcile without disclosing restricted information. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Omics Data Deposit Package Scenario Sensitivity MatrixUse when the omics public-deposition package readiness team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the deposition completeness manifest with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; required files and metadata reconcile without disclosing restricted information. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2
- Omics Data Deposit Package Scope Intake GateUse when a new omics public-deposition package readiness request needs a bounded work scope to produce a scoped intake card for the deposition completeness manifest. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; required files and metadata reconcile without disclosing restricted information. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refine...Votes: 0GitHub stars: 2
- Omics Data Deposit Package Source Provenance LedgerUse when a decision about omics public-deposition package readiness depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the deposition completeness manifest. Success means each material claim has a source, version/date, location, and confidence note; required files and metadata reconcile without disclosing restricted information. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. R...Votes: 0GitHub stars: 2
- Omics Data Deposit Package Threshold Rule CheckUse when a omics public-deposition package readiness decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the deposition completeness manifest 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; required files and metadata reconcile without disclosing restricted information. Use configured search, fetch,...Votes: 0GitHub stars: 2
- Omics Data Enrichment Universe Approval Evidence PacketUse when a functional enrichment universe selection result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the enrichment-universe audit 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 background matches the actual assay universe and every filter is documented. Use configured search, fetch, read...Votes: 0GitHub stars: 2
- Omics Data Enrichment Universe Change Impact TraceUse when a version, rule, source, or stakeholder change may affect functional enrichment universe selection to produce a before/after change record and impact map for the enrichment-universe audit. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the background matches the actual assay universe and every filter is documented. Use configured search, fetch, read, browser, test, and write capabilities only when r...Votes: 0GitHub stars: 2
- Omics Data Enrichment Universe Closeout Handoff LedgerUse when a functional enrichment universe selection work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the enrichment-universe audit 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 background matches the actual assay universe and every filter is documented. Use configured search, fetch, read, browser, test, and wr...Votes: 0GitHub stars: 2
- Omics Data Enrichment Universe Completeness ReconciliationUse when the functional enrichment universe selection workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the enrichment-universe audit 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 background matches the actual assay universe and every filter is documented. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Omics Data Enrichment Universe Exception Triage QueueUse when the functional enrichment universe selection workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the enrichment-universe audit 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 background matches the actual assay universe and every filter is documented. Use configured search, fetch, read, browser, test, and w...Votes: 0GitHub stars: 2
- Omics Data Enrichment Universe Recovery Readiness DrillUse when the functional enrichment universe selection workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the enrichment-universe audit 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 background matches the actual assay universe and every filter is documented. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Omics Data Enrichment Universe Scenario Sensitivity MatrixUse when the functional enrichment universe selection team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the enrichment-universe audit with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the background matches the actual assay universe and every filter is documented. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2
- Omics Data Enrichment Universe Scope Intake GateUse when a new functional enrichment universe selection request needs a bounded work scope to produce a scoped intake card for the enrichment-universe audit. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the background matches the actual assay universe and every filter is documented. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to ...Votes: 0GitHub stars: 2
- Omics Data Enrichment Universe Source Provenance LedgerUse when a decision about functional enrichment universe selection depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the enrichment-universe audit. Success means each material claim has a source, version/date, location, and confidence note; the background matches the actual assay universe and every filter is documented. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record ev...Votes: 0GitHub stars: 2
- Omics Data Enrichment Universe Threshold Rule CheckUse when a functional enrichment universe selection decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the enrichment-universe audit 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 background matches the actual assay universe and every filter is documented. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Omics Data Metagenomic Controls Approval Evidence PacketUse when a metagenomic negative-control interpretation result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the control-aware contamination review 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; candidate contamination is reported with evidence and uncertainty, not silently removed. Use configured...Votes: 0GitHub stars: 2
- Omics Data Metagenomic Controls Change Impact TraceUse when a version, rule, source, or stakeholder change may affect metagenomic negative-control interpretation to produce a before/after change record and impact map for the control-aware contamination review. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; candidate contamination is reported with evidence and uncertainty, not silently removed. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Omics Data Metagenomic Controls Closeout Handoff LedgerUse when a metagenomic negative-control interpretation work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the control-aware contamination review 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; candidate contamination is reported with evidence and uncertainty, not silently removed. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Omics Data Metagenomic Controls Completeness ReconciliationUse when the metagenomic negative-control interpretation workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the control-aware contamination review 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; candidate contamination is reported with evidence and uncertainty, not silently removed. Use configured search, ...Votes: 0GitHub stars: 2
- Omics Data Metagenomic Controls Exception Triage QueueUse when the metagenomic negative-control interpretation workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the control-aware contamination review 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; candidate contamination is reported with evidence and uncertainty, not silently removed. Use configured search, fetch, read, ...Votes: 0GitHub stars: 2
- Omics Data Metagenomic Controls Recovery Readiness DrillUse when the metagenomic negative-control interpretation workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the control-aware contamination review 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; candidate contamination is reported with evidence and uncertainty, not silently removed. Use configured search, fe...Votes: 0GitHub stars: 2
- Omics Data Metagenomic Controls Scenario Sensitivity MatrixUse when the metagenomic negative-control interpretation team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the control-aware contamination review with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; candidate contamination is reported with evidence and uncertainty, not silently removed. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Omics Data Metagenomic Controls Scope Intake GateUse when a new metagenomic negative-control interpretation request needs a bounded work scope to produce a scoped intake card for the control-aware contamination review. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; candidate contamination is reported with evidence and uncertainty, not silently removed. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, ...Votes: 0GitHub stars: 2
- Omics Data Metagenomic Controls Source Provenance LedgerUse when a decision about metagenomic negative-control interpretation depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the control-aware contamination review. Success means each material claim has a source, version/date, location, and confidence note; candidate contamination is reported with evidence and uncertainty, not silently removed. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and a...Votes: 0GitHub stars: 2
- Omics Data Metagenomic Controls Threshold Rule CheckUse when a metagenomic negative-control interpretation decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the control-aware contamination review 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; candidate contamination is reported with evidence and uncertainty, not silently removed. Use configured se...Votes: 0GitHub stars: 2
- Omics Data Multiomics Join Approval Evidence PacketUse when a multi-omics sample-link validation result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the cross-assay join audit 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; joins preserve the intended experimental unit and ambiguous matches remain unjoined. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Omics Data Multiomics Join Change Impact TraceUse when a version, rule, source, or stakeholder change may affect multi-omics sample-link validation to produce a before/after change record and impact map for the cross-assay join audit. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; joins preserve the intended experimental unit and ambiguous matches remain unjoined. Use configured search, fetch, read, browser, test, and write capabilities only when releva...Votes: 0GitHub stars: 2
- Omics Data Multiomics Join Closeout Handoff LedgerUse when a multi-omics sample-link validation work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the cross-assay join audit 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; joins preserve the intended experimental unit and ambiguous matches remain unjoined. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2
- Omics Data Multiomics Join Completeness ReconciliationUse when the multi-omics sample-link validation workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the cross-assay join audit 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; joins preserve the intended experimental unit and ambiguous matches remain unjoined. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Omics Data Multiomics Join Exception Triage QueueUse when the multi-omics sample-link validation workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the cross-assay join audit 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; joins preserve the intended experimental unit and ambiguous matches remain unjoined. Use configured search, fetch, read, browser, test, and write ...Votes: 0GitHub stars: 2
- Omics Data Multiomics Join Recovery Readiness DrillUse when the multi-omics sample-link validation workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the cross-assay join audit 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; joins preserve the intended experimental unit and ambiguous matches remain unjoined. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Omics Data Multiomics Join Scenario Sensitivity MatrixUse when the multi-omics sample-link validation team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the cross-assay join audit with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; joins preserve the intended experimental unit and ambiguous matches remain unjoined. Use configured search, fetch, read, browser, test, and write capabi...Votes: 0GitHub stars: 2
- Omics Data Multiomics Join Scope Intake GateUse when a new multi-omics sample-link validation request needs a bounded work scope to produce a scoped intake card for the cross-assay join audit. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; joins preserve the intended experimental unit and ambiguous matches remain unjoined. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three...Votes: 0GitHub stars: 2
- Omics Data Multiomics Join Source Provenance LedgerUse when a decision about multi-omics sample-link validation depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the cross-assay join audit. Success means each material claim has a source, version/date, location, and confidence note; joins preserve the intended experimental unit and ambiguous matches remain unjoined. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidenc...Votes: 0GitHub stars: 2
- Omics Data Multiomics Join Threshold Rule CheckUse when a multi-omics sample-link validation decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the cross-assay join audit 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; joins preserve the intended experimental unit and ambiguous matches remain unjoined. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Omics Data Proteomics Search Space Approval Evidence PacketUse when a proteomics search-space provenance result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the search-space configuration record 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 search can be reproduced against the exact database and parameter set. Use configured search, fetch, read, br...Votes: 0GitHub stars: 2
- Omics Data Proteomics Search Space Change Impact TraceUse when a version, rule, source, or stakeholder change may affect proteomics search-space provenance to produce a before/after change record and impact map for the search-space configuration record. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the search can be reproduced against the exact database and parameter set. Use configured search, fetch, read, browser, test, and write capabilities only when relev...Votes: 0GitHub stars: 2