All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Gtm Ops Content Source Provenance LedgerUse when a decision about commercial content governance depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the claim-source matrix. Success means each material claim has a source, version/date, location, and confidence note; every objective claim is current, sourced, and approved for the intended channel. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit re...Votes: 0GitHub stars: 2
- Gtm Ops Content Threshold Rule CheckUse when a commercial content governance decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the claim-source 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; every objective claim is current, sourced, and approved for the intended channel. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Gtm Ops Crm Hygiene Approval Evidence PacketUse when a CRM data quality result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the CRM exception worklist 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 proposed correction has a source and ambiguous merges are escalated. Use configured search, fetch, read, browser, test, and write capabil...Votes: 0GitHub stars: 2
- Gtm Ops Crm Hygiene Change Impact TraceUse when a version, rule, source, or stakeholder change may affect CRM data quality to produce a before/after change record and impact map for the CRM exception worklist. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each proposed correction has a source and ambiguous merges are escalated. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evi...Votes: 0GitHub stars: 2
- Gtm Ops Crm Hygiene Closeout Handoff LedgerUse when a CRM data quality work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the CRM exception worklist 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 proposed correction has a source and ambiguous merges are escalated. Use configured search, fetch, read, browser, test, and write capabilities only when relevan...Votes: 0GitHub stars: 2
- Gtm Ops Crm Hygiene Completeness ReconciliationUse when the CRM data quality workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the CRM exception worklist 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 proposed correction has a source and ambiguous merges are escalated. Use configured search, fetch, read, browser, test, and write capabilities onl...Votes: 0GitHub stars: 2
- Gtm Ops Crm Hygiene Exception Triage QueueUse when the CRM data quality workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the CRM exception worklist 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 proposed correction has a source and ambiguous merges are escalated. Use configured search, fetch, read, browser, test, and write capabilities only when releva...Votes: 0GitHub stars: 2
- Gtm Ops Crm Hygiene Recovery Readiness DrillUse when the CRM data quality workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the CRM exception worklist 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 proposed correction has a source and ambiguous merges are escalated. Use configured search, fetch, read, browser, test, and write capabilities only ...Votes: 0GitHub stars: 2
- Gtm Ops Crm Hygiene Scenario Sensitivity MatrixUse when the CRM data quality team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the CRM exception worklist with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each proposed correction has a source and ambiguous merges are escalated. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and...Votes: 0GitHub stars: 2
- Gtm Ops Crm Hygiene Scope Intake GateUse when a new CRM data quality request needs a bounded work scope to produce a scoped intake card for the CRM exception worklist. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each proposed correction has a source and ambiguous merges are escalated. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and seek app...Votes: 0GitHub stars: 2
- Gtm Ops Crm Hygiene Source Provenance LedgerUse when a decision about CRM data quality depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the CRM exception worklist. Success means each material claim has a source, version/date, location, and confidence note; each proposed correction has a source and ambiguous merges are escalated. 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
- Gtm Ops Crm Hygiene Threshold Rule CheckUse when a CRM data quality decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the CRM exception worklist 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 proposed correction has a source and ambiguous merges are escalated. Use configured search, fetch, read, browser, test, and write capabiliti...Votes: 0GitHub stars: 2
- Gtm Ops Deal Room Approval Evidence PacketUse when a deal and opportunity operations result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the deal review packet 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; stage and forecast rationale are evidence-backed, not inferred from activity volume. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Gtm Ops Deal Room Change Impact TraceUse when a version, rule, source, or stakeholder change may affect deal and opportunity operations to produce a before/after change record and impact map for the deal review packet. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; stage and forecast rationale are evidence-backed, not inferred from activity volume. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and ...Votes: 0GitHub stars: 2
- Gtm Ops Deal Room Closeout Handoff LedgerUse when a deal and opportunity operations work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the deal review packet 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; stage and forecast rationale are evidence-backed, not inferred from activity volume. Use configured search, fetch, read, browser, test, and write capabili...Votes: 0GitHub stars: 2
- Gtm Ops Deal Room Completeness ReconciliationUse when the deal and opportunity operations workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the deal review packet 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; stage and forecast rationale are evidence-backed, not inferred from activity volume. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Gtm Ops Deal Room Exception Triage QueueUse when the deal and opportunity operations workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the deal review 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; stage and forecast rationale are evidence-backed, not inferred from activity volume. Use configured search, fetch, read, browser, test, and write capabil...Votes: 0GitHub stars: 2
- Gtm Ops Deal Room Recovery Readiness DrillUse when the deal and opportunity operations workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the deal review 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; stage and forecast rationale are evidence-backed, not inferred from activity volume. Use configured search, fetch, read, browser, test, and wr...Votes: 0GitHub stars: 2
- Gtm Ops Deal Room Scenario Sensitivity MatrixUse when the deal and opportunity operations team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the deal review packet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; stage and forecast rationale are evidence-backed, not inferred from activity volume. Use configured search, fetch, read, browser, test, and write capabilities ...Votes: 0GitHub stars: 2
- Gtm Ops Deal Room Scope Intake GateUse when a new deal and opportunity operations request needs a bounded work scope to produce a scoped intake card for the deal review packet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; stage and forecast rationale are evidence-backed, not inferred from activity volume. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focuse...Votes: 0GitHub stars: 2
- Gtm Ops Deal Room Source Provenance LedgerUse when a decision about deal and opportunity operations depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the deal review packet. Success means each material claim has a source, version/date, location, and confidence note; stage and forecast rationale are evidence-backed, not inferred from activity volume. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limi...Votes: 0GitHub stars: 2
- Gtm Ops Deal Room Threshold Rule CheckUse when a deal and opportunity operations decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the deal review 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; stage and forecast rationale are evidence-backed, not inferred from activity volume. Use configured search, fetch, read, browser, test...Votes: 0GitHub stars: 2
- Gtm Ops Onboarding Approval Evidence PacketUse when a customer onboarding result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the onboarding milestone plan 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 milestone has an owner, dependency, date, and observable acceptance signal. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Gtm Ops Onboarding Change Impact TraceUse when a version, rule, source, or stakeholder change may affect customer onboarding to produce a before/after change record and impact map for the onboarding milestone plan. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each milestone has an owner, dependency, date, and observable acceptance signal. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorize...Votes: 0GitHub stars: 2
- Gtm Ops Onboarding Closeout Handoff LedgerUse when a customer onboarding work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the onboarding milestone plan 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 milestone has an owner, dependency, date, and observable acceptance signal. Use configured search, fetch, read, browser, test, and write capabilities only...Votes: 0GitHub stars: 2
- Gtm Ops Onboarding Completeness ReconciliationUse when the customer onboarding workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the onboarding milestone plan 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 milestone has an owner, dependency, date, and observable acceptance signal. Use configured search, fetch, read, browser, test, and write cap...Votes: 0GitHub stars: 2
- Gtm Ops Onboarding Exception Triage QueueUse when the customer onboarding workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the onboarding milestone plan 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 milestone has an owner, dependency, date, and observable acceptance signal. Use configured search, fetch, read, browser, test, and write capabilities onl...Votes: 0GitHub stars: 2
- Gtm Ops Onboarding Recovery Readiness DrillUse when the customer onboarding workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the onboarding milestone plan 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 milestone has an owner, dependency, date, and observable acceptance signal. Use configured search, fetch, read, browser, test, and write capab...Votes: 0GitHub stars: 2
- Gtm Ops Onboarding Scenario Sensitivity MatrixUse when the customer onboarding team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the onboarding milestone plan with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each milestone has an owner, dependency, date, and observable acceptance signal. Use configured search, fetch, read, browser, test, and write capabilities only when...Votes: 0GitHub stars: 2
- Gtm Ops Onboarding Scope Intake GateUse when a new customer onboarding request needs a bounded work scope to produce a scoped intake card for the onboarding milestone plan. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each milestone has an owner, dependency, date, and observable acceptance signal. 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
- Gtm Ops Onboarding Source Provenance LedgerUse when a decision about customer onboarding depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the onboarding milestone plan. Success means each material claim has a source, version/date, location, and confidence note; each milestone has an owner, dependency, date, and observable acceptance signal. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinem...Votes: 0GitHub stars: 2
- Gtm Ops Onboarding Threshold Rule CheckUse when a customer onboarding decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the onboarding milestone plan 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 milestone has an owner, dependency, date, and observable acceptance signal. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Gtm Ops Prospecting Approval Evidence PacketUse when a prospecting qualification result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the lead research brief 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; every included signal is sourced and excluded contacts remain excluded. Use configured search, fetch, read, browser, test, and write cap...Votes: 0GitHub stars: 2
- Gtm Ops Prospecting Change Impact TraceUse when a version, rule, source, or stakeholder change may affect prospecting qualification to produce a before/after change record and impact map for the lead research brief. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; every included signal is sourced and excluded contacts remain excluded. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record...Votes: 0GitHub stars: 2
- Gtm Ops Prospecting Closeout Handoff LedgerUse when a prospecting qualification work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the lead research brief 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; every included signal is sourced and excluded contacts remain excluded. Use configured search, fetch, read, browser, test, and write capabilities only when rel...Votes: 0GitHub stars: 2
- Gtm Ops Prospecting Completeness ReconciliationUse when the prospecting qualification workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the lead research 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; every included signal is sourced and excluded contacts remain excluded. Use configured search, fetch, read, browser, test, and write capabilities...Votes: 0GitHub stars: 2
- Gtm Ops Prospecting Exception Triage QueueUse when the prospecting qualification workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the lead research 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; every included signal is sourced and excluded contacts remain excluded. Use configured search, fetch, read, browser, test, and write capabilities only when re...Votes: 0GitHub stars: 2
- Gtm Ops Prospecting Recovery Readiness DrillUse when the prospecting qualification workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the lead research 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; every included signal is sourced and excluded contacts remain excluded. Use configured search, fetch, read, browser, test, and write capabilities o...Votes: 0GitHub stars: 2
- Gtm Ops Prospecting Scenario Sensitivity MatrixUse when the prospecting qualification team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the lead research brief with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; every included signal is sourced and excluded contacts remain excluded. Use configured search, fetch, read, browser, test, and write capabilities only when relevant...Votes: 0GitHub stars: 2
- Gtm Ops Prospecting Scope Intake GateUse when a new prospecting qualification request needs a bounded work scope to produce a scoped intake card for the lead research brief. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; every included signal is sourced and excluded contacts remain excluded. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and seek...Votes: 0GitHub stars: 2
- Gtm Ops Prospecting Source Provenance LedgerUse when a decision about prospecting qualification depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the lead research brief. Success means each material claim has a source, version/date, location, and confidence note; every included signal is sourced and excluded contacts remain excluded. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to th...Votes: 0GitHub stars: 2
- Gtm Ops Prospecting Threshold Rule CheckUse when a prospecting qualification decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the lead research 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; every included signal is sourced and excluded contacts remain excluded. Use configured search, fetch, read, browser, test, and write capabi...Votes: 0GitHub stars: 2
- Gtm Ops Renewal Approval Evidence PacketUse when a renewal and expansion readiness result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the renewal decision packet 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 risk or expansion signal has evidence and commercial terms remain unaltered. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Gtm Ops Renewal Change Impact TraceUse when a version, rule, source, or stakeholder change may affect renewal and expansion readiness to produce a before/after change record and impact map for the renewal decision packet. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each risk or expansion signal has evidence and commercial terms remain unaltered. Use configured search, fetch, read, browser, test, and write capabilities only when relevant an...Votes: 0GitHub stars: 2
- Gtm Ops Renewal Closeout Handoff LedgerUse when a renewal and expansion readiness work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the renewal decision packet 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 risk or expansion signal has evidence and commercial terms remain unaltered. Use configured search, fetch, read, browser, test, and write capabi...Votes: 0GitHub stars: 2
- Gtm Ops Renewal Completeness ReconciliationUse when the renewal and expansion readiness workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the renewal decision packet 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 risk or expansion signal has evidence and commercial terms remain unaltered. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Gtm Ops Renewal Exception Triage QueueUse when the renewal and expansion readiness workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the renewal decision 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; each risk or expansion signal has evidence and commercial terms remain unaltered. Use configured search, fetch, read, browser, test, and write capab...Votes: 0GitHub stars: 2
- Gtm Ops Renewal Recovery Readiness DrillUse when the renewal and expansion readiness workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the renewal decision 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; each risk or expansion signal has evidence and commercial terms remain unaltered. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Gtm Ops Renewal Scenario Sensitivity MatrixUse when the renewal and expansion readiness team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the renewal decision packet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each risk or expansion signal has evidence and commercial terms remain unaltered. Use configured search, fetch, read, browser, test, and write capabilitie...Votes: 0GitHub stars: 2
- Gtm Ops Renewal Scope Intake GateUse when a new renewal and expansion readiness request needs a bounded work scope to produce a scoped intake card for the renewal decision packet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each risk or expansion signal has evidence and commercial terms remain unaltered. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focu...Votes: 0GitHub stars: 2