All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Growth Evidence Incrementality Readout Completeness ReconciliationUse when the campaign incrementality readout workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the incrementality evidence brief 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; causal language matches the design and limitations are explicit. Use configured search, fetch, read, browser, test, and write cap...Votes: 0GitHub stars: 2
- Growth Evidence Incrementality Readout Exception Triage QueueUse when the campaign incrementality readout workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the incrementality evidence brief 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; causal language matches the design and limitations are explicit. Use configured search, fetch, read, browser, test, and write capabilities onl...Votes: 0GitHub stars: 2
- Growth Evidence Incrementality Readout Recovery Readiness DrillUse when the campaign incrementality readout workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the incrementality evidence brief 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; causal language matches the design and limitations are explicit. Use configured search, fetch, read, browser, test, and write capab...Votes: 0GitHub stars: 2
- Growth Evidence Incrementality Readout Scenario Sensitivity MatrixUse when the campaign incrementality readout team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the incrementality evidence brief with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; causal language matches the design and limitations are explicit. Use configured search, fetch, read, browser, test, and write capabilities only when...Votes: 0GitHub stars: 2
- Growth Evidence Incrementality Readout Scope Intake GateUse when a new campaign incrementality readout request needs a bounded work scope to produce a scoped intake card for the incrementality evidence brief. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; causal language matches the design and limitations are explicit. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes,...Votes: 0GitHub stars: 2
- Growth Evidence Incrementality Readout Source Provenance LedgerUse when a decision about campaign incrementality readout depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the incrementality evidence brief. Success means each material claim has a source, version/date, location, and confidence note; causal language matches the design and limitations are explicit. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinem...Votes: 0GitHub stars: 2
- Growth Evidence Incrementality Readout Threshold Rule CheckUse when a campaign incrementality readout decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the incrementality evidence brief 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; causal language matches the design and limitations are explicit. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Growth Evidence Landing Measurement Approval Evidence PacketUse when a landing-page measurement design result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the landing-page event map 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; events distinguish actual user actions from page loads and consent state is respected. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Growth Evidence Landing Measurement Change Impact TraceUse when a version, rule, source, or stakeholder change may affect landing-page measurement design to produce a before/after change record and impact map for the landing-page event map. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; events distinguish actual user actions from page loads and consent state is respected. Use configured search, fetch, read, browser, test, and write capabilities only when relevan...Votes: 0GitHub stars: 2
- Growth Evidence Landing Measurement Closeout Handoff LedgerUse when a landing-page measurement design work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the landing-page event map 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; events distinguish actual user actions from page loads and consent state is respected. Use configured search, fetch, read, browser, test, and write ca...Votes: 0GitHub stars: 2
- Growth Evidence Landing Measurement Completeness ReconciliationUse when the landing-page measurement design workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the landing-page event map 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; events distinguish actual user actions from page loads and consent state is respected. Use configured search, fetch, read, browser, test...Votes: 0GitHub stars: 2
- Growth Evidence Landing Measurement Exception Triage QueueUse when the landing-page measurement design workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the landing-page event map 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 distinguish actual user actions from page loads and consent state is respected. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2
- Growth Evidence Landing Measurement Recovery Readiness DrillUse when the landing-page measurement design workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the landing-page event map 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 distinguish actual user actions from page loads and consent state is respected. Use configured search, fetch, read, browser, test, ...Votes: 0GitHub stars: 2
- Growth Evidence Landing Measurement Scenario Sensitivity MatrixUse when the landing-page measurement design team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the landing-page event map with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; events distinguish actual user actions from page loads and consent state is respected. Use configured search, fetch, read, browser, test, and write capabil...Votes: 0GitHub stars: 2
- Growth Evidence Landing Measurement Scope Intake GateUse when a new landing-page measurement design request needs a bounded work scope to produce a scoped intake card for the landing-page event map. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; events distinguish actual user actions from page loads and consent state is respected. 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
- Growth Evidence Landing Measurement Source Provenance LedgerUse when a decision about landing-page measurement design depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the landing-page event map. Success means each material claim has a source, version/date, location, and confidence note; events distinguish actual user actions from page loads and consent state is respected. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence...Votes: 0GitHub stars: 2
- Growth Evidence Landing Measurement Threshold Rule CheckUse when a landing-page measurement design decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the landing-page event map 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 distinguish actual user actions from page loads and consent state is respected. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Growth Evidence Lifecycle Segmentation Approval Evidence PacketUse when a lifecycle campaign segmentation rules result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the lifecycle segment specification 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; test records enter or exit for explainable reasons and no message is sent. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Growth Evidence Lifecycle Segmentation Change Impact TraceUse when a version, rule, source, or stakeholder change may affect lifecycle campaign segmentation rules to produce a before/after change record and impact map for the lifecycle segment specification. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; test records enter or exit for explainable reasons and no message is sent. Use configured search, fetch, read, browser, test, and write capabilities only when rele...Votes: 0GitHub stars: 2
- Growth Evidence Lifecycle Segmentation Closeout Handoff LedgerUse when a lifecycle campaign segmentation rules work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the lifecycle segment specification 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; test records enter or exit for explainable reasons and no message is sent. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Growth Evidence Lifecycle Segmentation Completeness ReconciliationUse when the lifecycle campaign segmentation rules workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the lifecycle segment specification 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; test records enter or exit for explainable reasons and no message is sent. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Growth Evidence Lifecycle Segmentation Exception Triage QueueUse when the lifecycle campaign segmentation rules workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the lifecycle segment specification 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; test records enter or exit for explainable reasons and no message is sent. Use configured search, fetch, read, browser, test, and writ...Votes: 0GitHub stars: 2
- Growth Evidence Lifecycle Segmentation Recovery Readiness DrillUse when the lifecycle campaign segmentation rules workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the lifecycle segment specification 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; test records enter or exit for explainable reasons and no message is sent. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Growth Evidence Lifecycle Segmentation Scenario Sensitivity MatrixUse when the lifecycle campaign segmentation rules team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the lifecycle segment specification with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; test records enter or exit for explainable reasons and no message is sent. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Growth Evidence Lifecycle Segmentation Scope Intake GateUse when a new lifecycle campaign segmentation rules request needs a bounded work scope to produce a scoped intake card for the lifecycle segment specification. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; test records enter or exit for explainable reasons and no message is sent. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to thr...Votes: 0GitHub stars: 2
- Growth Evidence Lifecycle Segmentation Source Provenance LedgerUse when a decision about lifecycle campaign segmentation rules depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the lifecycle segment specification. Success means each material claim has a source, version/date, location, and confidence note; test records enter or exit for explainable reasons and no message is sent. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evide...Votes: 0GitHub stars: 2
- Growth Evidence Lifecycle Segmentation Threshold Rule CheckUse when a lifecycle campaign segmentation rules decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the lifecycle segment specification 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; test records enter or exit for explainable reasons and no message is sent. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Growth Evidence Positioning Claims Approval Evidence PacketUse when a marketing positioning and claim substantiation result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the positioning claim 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; each external claim has current evidence and unsupported comparisons are removed from draft. Use configured se...Votes: 0GitHub stars: 2
- Growth Evidence Positioning Claims Change Impact TraceUse when a version, rule, source, or stakeholder change may affect marketing positioning and claim substantiation to produce a before/after change record and impact map for the positioning claim matrix. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each external claim has current evidence and unsupported comparisons are removed from draft. Use configured search, fetch, read, browser, test, and write capabil...Votes: 0GitHub stars: 2
- Growth Evidence Positioning Claims Closeout Handoff LedgerUse when a marketing positioning and claim substantiation work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the positioning claim 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; each external claim has current evidence and unsupported comparisons are removed from draft. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Growth Evidence Positioning Claims Completeness ReconciliationUse when the marketing positioning and claim substantiation workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the positioning claim 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; each external claim has current evidence and unsupported comparisons are removed from draft. Use configured search, fet...Votes: 0GitHub stars: 2
- Growth Evidence Positioning Claims Exception Triage QueueUse when the marketing positioning and claim substantiation workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the positioning claim 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; each external claim has current evidence and unsupported comparisons are removed from draft. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Growth Evidence Positioning Claims Recovery Readiness DrillUse when the marketing positioning and claim substantiation workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the positioning claim 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; each external claim has current evidence and unsupported comparisons are removed from draft. Use configured search, fetch...Votes: 0GitHub stars: 2
- Growth Evidence Positioning Claims Scenario Sensitivity MatrixUse when the marketing positioning and claim substantiation team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the positioning claim matrix with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each external claim has current evidence and unsupported comparisons are removed from draft. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Growth Evidence Positioning Claims Scope Intake GateUse when a new marketing positioning and claim substantiation request needs a bounded work scope to produce a scoped intake card for the positioning claim matrix. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each external claim has current evidence and unsupported comparisons are removed from draft. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, lim...Votes: 0GitHub stars: 2
- Growth Evidence Positioning Claims Source Provenance LedgerUse when a decision about marketing positioning and claim substantiation depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the positioning claim matrix. Success means each material claim has a source, version/date, location, and confidence note; each external claim has current evidence and unsupported comparisons are removed from draft. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and auth...Votes: 0GitHub stars: 2
- Growth Evidence Positioning Claims Threshold Rule CheckUse when a marketing positioning and claim substantiation decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the positioning claim 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; each external claim has current evidence and unsupported comparisons are removed from draft. Use configured searc...Votes: 0GitHub stars: 2
- Growth Evidence Problem Evidence Approval Evidence PacketUse when a customer problem evidence result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the problem-evidence map 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 problem statement traces to multiple evidence types or is labeled as a hypothesis. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Growth Evidence Problem Evidence Change Impact TraceUse when a version, rule, source, or stakeholder change may affect customer problem evidence to produce a before/after change record and impact map for the problem-evidence map. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each problem statement traces to multiple evidence types or is labeled as a hypothesis. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and a...Votes: 0GitHub stars: 2
- Growth Evidence Problem Evidence Closeout Handoff LedgerUse when a customer problem evidence work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the problem-evidence map 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 problem statement traces to multiple evidence types or is labeled as a hypothesis. Use configured search, fetch, read, browser, test, and write capabilit...Votes: 0GitHub stars: 2
- Growth Evidence Problem Evidence Completeness ReconciliationUse when the customer problem evidence workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the problem-evidence map 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 problem statement traces to multiple evidence types or is labeled as a hypothesis. Use configured search, fetch, read, browser, test, and w...Votes: 0GitHub stars: 2
- Growth Evidence Problem Evidence Exception Triage QueueUse when the customer problem evidence workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the problem-evidence map 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 problem statement traces to multiple evidence types or is labeled as a hypothesis. Use configured search, fetch, read, browser, test, and write capabili...Votes: 0GitHub stars: 2
- Growth Evidence Problem Evidence Recovery Readiness DrillUse when the customer problem evidence workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the problem-evidence map 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 problem statement traces to multiple evidence types or is labeled as a hypothesis. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Growth Evidence Problem Evidence Scenario Sensitivity MatrixUse when the customer problem evidence team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the problem-evidence map with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each problem statement traces to multiple evidence types or is labeled as a hypothesis. Use configured search, fetch, read, browser, test, and write capabilities o...Votes: 0GitHub stars: 2
- Growth Evidence Problem Evidence Scope Intake GateUse when a new customer problem evidence request needs a bounded work scope to produce a scoped intake card for the problem-evidence map. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each problem statement traces to multiple evidence types or is labeled as a hypothesis. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused...Votes: 0GitHub stars: 2
- Growth Evidence Problem Evidence Source Provenance LedgerUse when a decision about customer problem evidence depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the problem-evidence map. Success means each material claim has a source, version/date, location, and confidence note; each problem statement traces to multiple evidence types or is labeled as a hypothesis. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit...Votes: 0GitHub stars: 2
- Growth Evidence Problem Evidence Threshold Rule CheckUse when a customer problem evidence decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the problem-evidence map 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 problem statement traces to multiple evidence types or is labeled as a hypothesis. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Growth Evidence Referral Source Approval Evidence PacketUse when a referral and partner-source quality result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the referral-source 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; source assignments reconcile to the taxonomy and missing values remain visible. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Growth Evidence Referral Source Change Impact TraceUse when a version, rule, source, or stakeholder change may affect referral and partner-source quality to produce a before/after change record and impact map for the referral-source reconciliation. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; source assignments reconcile to the taxonomy and missing values remain visible. Use configured search, fetch, read, browser, test, and write capabilities only when re...Votes: 0GitHub stars: 2
- Growth Evidence Referral Source Closeout Handoff LedgerUse when a referral and partner-source quality work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the referral-source 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; source assignments reconcile to the taxonomy and missing values remain visible. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2