All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Gtm Ops Renewal Source Provenance LedgerUse when a decision about renewal and expansion readiness depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the renewal decision packet. Success means each material claim has a source, version/date, location, and confidence note; 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, li...Votes: 0GitHub stars: 2
- Gtm Ops Renewal Threshold Rule CheckUse when a renewal and expansion readiness decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the renewal decision 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; each risk or expansion signal has evidence and commercial terms remain unaltered. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Gtm Ops Support Voice Approval Evidence PacketUse when a support and voice-of-customer result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the support theme register 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 theme has representative evidence and privacy-safe aggregation. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Gtm Ops Support Voice Change Impact TraceUse when a version, rule, source, or stakeholder change may affect support and voice-of-customer to produce a before/after change record and impact map for the support theme register. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each theme has representative evidence and privacy-safe aggregation. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Re...Votes: 0GitHub stars: 2
- Gtm Ops Support Voice Closeout Handoff LedgerUse when a support and voice-of-customer work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the support theme register 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 theme has representative evidence and privacy-safe aggregation. Use configured search, fetch, read, browser, test, and write capabilities only when...Votes: 0GitHub stars: 2
- Gtm Ops Support Voice Completeness ReconciliationUse when the support and voice-of-customer workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the support theme register 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 theme has representative evidence and privacy-safe aggregation. Use configured search, fetch, read, browser, test, and write capabili...Votes: 0GitHub stars: 2
- Gtm Ops Support Voice Exception Triage QueueUse when the support and voice-of-customer workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the support theme register 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 theme has representative evidence and privacy-safe aggregation. Use configured search, fetch, read, browser, test, and write capabilities only whe...Votes: 0GitHub stars: 2
- Gtm Ops Support Voice Recovery Readiness DrillUse when the support and voice-of-customer workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the support theme register 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 theme has representative evidence and privacy-safe aggregation. Use configured search, fetch, read, browser, test, and write capabiliti...Votes: 0GitHub stars: 2
- Gtm Ops Support Voice Scenario Sensitivity MatrixUse when the support and voice-of-customer team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the support theme register with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each theme has representative evidence and privacy-safe aggregation. Use configured search, fetch, read, browser, test, and write capabilities only when rele...Votes: 0GitHub stars: 2
- Gtm Ops Support Voice Scope Intake GateUse when a new support and voice-of-customer request needs a bounded work scope to produce a scoped intake card for the support theme register. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each theme has representative evidence and privacy-safe aggregation. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and ...Votes: 0GitHub stars: 2
- Gtm Ops Support Voice Source Provenance LedgerUse when a decision about support and voice-of-customer depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the support theme register. Success means each material claim has a source, version/date, location, and confidence note; each theme has representative evidence and privacy-safe aggregation. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement t...Votes: 0GitHub stars: 2
- Gtm Ops Support Voice Threshold Rule CheckUse when a support and voice-of-customer decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the support theme register 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 theme has representative evidence and privacy-safe aggregation. Use configured search, fetch, read, browser, test, and write ca...Votes: 0GitHub stars: 2
- Instagram Automation Capability Surface MapUse when the actual capability boundary of Instagram account operations needs to be distinguished from assumptions. Produce a capability map for Instagram account operations covering the requested behavior, verified support, exclusions, and unknowns. Success means each in-scope capability is tied to local configuration, a version-matched authoritative reference, or an observed non-production result, and all unknowns remain explicit. The review is bounded to account identity, media format, acc...Votes: 0GitHub stars: 2
- Instagram Automation Change Impact AssessmentUse when a proposed Instagram account operations version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Instagram account operations with baseline, affected dependencies, validation needs, and recovery boundary. Success means affected dependencies and compatibility assumptions are evidenced, unknown consumers are named as unknown, and no migration or rollout is implied. The review is bounded to account identity, media format, a...Votes: 0GitHub stars: 2
- Instagram Automation Failure Triage RecordUse when a reproducible Instagram account operations symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Instagram account operations with symptom, environment, evidence, hypothesis, and next safe check. Success means the diagnosis distinguishes observation from inference, each proposed check is reversible and scoped, and unresolved causes remain open. The review is bounded to account identity, media format, access scope, audience consent, and pub...Votes: 0GitHub stars: 2
- Instagram Automation Input Output ContractUse when the accepted inputs or produced outputs for Instagram account operations need a checkable boundary. Produce an input/output contract for Instagram account operations with types, required fields, exclusions, and representative approved fixtures. Success means the contract names its source and version, boundary cases are visible, and no private or unapproved payload is needed to explain the result. The review is bounded to account identity, media format, access scope, audience consent,...Votes: 0GitHub stars: 2
- Instagram Automation Integration Parity TraceUse when Instagram account operations exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Instagram account operations showing source, transformation, destination, and observed result. Success means each material field or state transition has a traceable mapping and observed mismatches are separated from assumptions. The review is bounded to account identity, media format, access scope, audience consent, and publish boun...Votes: 0GitHub stars: 2
- Instagram Automation Performance EnvelopeUse when Instagram account operations must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Instagram account operations with test conditions, baseline, observed range, and limitations. Success means conditions and measurements are reproducible, the comparison uses the stated budget, and limitations or resource costs are visible. The review is bounded to account identity, media format, access scope, audienc...Votes: 0GitHub stars: 2
- Instagram Automation Permission Boundary ReviewUse when Instagram account operations may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Instagram account operations showing identity, requested capability, data scope, and approval gate. Success means every sensitive capability has a named authorization boundary, unnecessary data and privileges are called out, and no action is treated as approved by implication. The review is bounded to account identity, media format, access sco...Votes: 0GitHub stars: 2
- Instagram Automation Release Handoff RecordUse when a Instagram account operations review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Instagram account operations with version, evidence, open issues, approval state, and safe next step. Success means the receiver can distinguish verified facts, proposals, approvals, and unknowns, and no publication, deployment, write, or contact is claimed unless independently confirmed. The review is bounded to account identity, media format, acc...Votes: 0GitHub stars: 2
- Instagram Automation Reproducibility Fixture PlanUse when a Instagram account operations result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Instagram account operations defining fixture identity, environment, expected observations, and cleanup boundary. Success means another reviewer can identify the fixture and environment, distinguish expected from observed behavior, and repeat the check without an unapproved external effect. The review is bounded to account...Votes: 0GitHub stars: 2
- Instagram Automation Version CompatibilityUse when a Instagram account operations integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Instagram account operations with exact versions, supported combinations, and open questions. Success means the tested version tuple is explicit, each compatibility claim has a dated source or local result, and unsupported combinations are not presented as working. The review is bounded to account identity, media format...Votes: 0GitHub stars: 2
- Klaviyo Automation Capability Surface MapUse when the actual capability boundary of Klaviyo lifecycle messaging operations needs to be distinguished from assumptions. Produce a capability map for Klaviyo lifecycle messaging operations covering the requested behavior, verified support, exclusions, and unknowns. Success means each in-scope capability is tied to local configuration, a version-matched authoritative reference, or an observed non-production result, and all unknowns remain explicit. The review is bounded to profile identit...Votes: 0GitHub stars: 2
- Klaviyo Automation Change Impact AssessmentUse when a proposed Klaviyo lifecycle messaging operations version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Klaviyo lifecycle messaging operations with baseline, affected dependencies, validation needs, and recovery boundary. Success means affected dependencies and compatibility assumptions are evidenced, unknown consumers are named as unknown, and no migration or rollout is implied. The review is bounded to profile ident...Votes: 0GitHub stars: 2
- Klaviyo Automation Failure Triage RecordUse when a reproducible Klaviyo lifecycle messaging operations symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Klaviyo lifecycle messaging operations with symptom, environment, evidence, hypothesis, and next safe check. Success means the diagnosis distinguishes observation from inference, each proposed check is reversible and scoped, and unresolved causes remain open. The review is bounded to profile identity, consent state, segment logic, cam...Votes: 0GitHub stars: 2
- Klaviyo Automation Input Output ContractUse when the accepted inputs or produced outputs for Klaviyo lifecycle messaging operations need a checkable boundary. Produce an input/output contract for Klaviyo lifecycle messaging operations with types, required fields, exclusions, and representative approved fixtures. Success means the contract names its source and version, boundary cases are visible, and no private or unapproved payload is needed to explain the result. The review is bounded to profile identity, consent state, segment lo...Votes: 0GitHub stars: 2
- Klaviyo Automation Integration Parity TraceUse when Klaviyo lifecycle messaging operations exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Klaviyo lifecycle messaging operations showing source, transformation, destination, and observed result. Success means each material field or state transition has a traceable mapping and observed mismatches are separated from assumptions. The review is bounded to profile identity, consent state, segment logic, campaign sta...Votes: 0GitHub stars: 2
- Klaviyo Automation Performance EnvelopeUse when Klaviyo lifecycle messaging operations must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Klaviyo lifecycle messaging operations with test conditions, baseline, observed range, and limitations. Success means conditions and measurements are reproducible, the comparison uses the stated budget, and limitations or resource costs are visible. The review is bounded to profile identity, consent state, ...Votes: 0GitHub stars: 2
- Klaviyo Automation Permission Boundary ReviewUse when Klaviyo lifecycle messaging operations may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Klaviyo lifecycle messaging operations showing identity, requested capability, data scope, and approval gate. Success means every sensitive capability has a named authorization boundary, unnecessary data and privileges are called out, and no action is treated as approved by implication. The review is bounded to profile identity, cons...Votes: 0GitHub stars: 2
- Klaviyo Automation Release Handoff RecordUse when a Klaviyo lifecycle messaging operations review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Klaviyo lifecycle messaging operations with version, evidence, open issues, approval state, and safe next step. Success means the receiver can distinguish verified facts, proposals, approvals, and unknowns, and no publication, deployment, write, or contact is claimed unless independently confirmed. The review is bounded to profile identit...Votes: 0GitHub stars: 2
- Klaviyo Automation Reproducibility Fixture PlanUse when a Klaviyo lifecycle messaging operations result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Klaviyo lifecycle messaging operations defining fixture identity, environment, expected observations, and cleanup boundary. Success means another reviewer can identify the fixture and environment, distinguish expected from observed behavior, and repeat the check without an unapproved external effect. The review i...Votes: 0GitHub stars: 2
- Klaviyo Automation Version CompatibilityUse when a Klaviyo lifecycle messaging operations integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Klaviyo lifecycle messaging operations with exact versions, supported combinations, and open questions. Success means the tested version tuple is explicit, each compatibility claim has a dated source or local result, and unsupported combinations are not presented as working. The review is bounded to profile id...Votes: 0GitHub stars: 2
- Linkedin Automation Capability Surface MapUse when the actual capability boundary of LinkedIn workspace operations needs to be distinguished from assumptions. Produce a capability map for LinkedIn workspace operations covering the requested behavior, verified support, exclusions, and unknowns. Success means each in-scope capability is tied to local configuration, a version-matched authoritative reference, or an observed non-production result, and all unknowns remain explicit. The review is bounded to member or organization identity, ...Votes: 0GitHub stars: 2
- Linkedin Automation Change Impact AssessmentUse when a proposed LinkedIn workspace operations version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for LinkedIn workspace operations with baseline, affected dependencies, validation needs, and recovery boundary. Success means affected dependencies and compatibility assumptions are evidenced, unknown consumers are named as unknown, and no migration or rollout is implied. The review is bounded to member or organization identity...Votes: 0GitHub stars: 2
- Linkedin Automation Failure Triage RecordUse when a reproducible LinkedIn workspace operations symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for LinkedIn workspace operations with symptom, environment, evidence, hypothesis, and next safe check. Success means the diagnosis distinguishes observation from inference, each proposed check is reversible and scoped, and unresolved causes remain open. The review is bounded to member or organization identity, profile scope, content state, and ou...Votes: 0GitHub stars: 2
- Linkedin Automation Input Output ContractUse when the accepted inputs or produced outputs for LinkedIn workspace operations need a checkable boundary. Produce an input/output contract for LinkedIn workspace operations with types, required fields, exclusions, and representative approved fixtures. Success means the contract names its source and version, boundary cases are visible, and no private or unapproved payload is needed to explain the result. The review is bounded to member or organization identity, profile scope, content state...Votes: 0GitHub stars: 2
- Linkedin Automation Integration Parity TraceUse when LinkedIn workspace operations exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for LinkedIn workspace operations showing source, transformation, destination, and observed result. Success means each material field or state transition has a traceable mapping and observed mismatches are separated from assumptions. The review is bounded to member or organization identity, profile scope, content state, and outbound-ac...Votes: 0GitHub stars: 2
- Linkedin Automation Performance EnvelopeUse when LinkedIn workspace operations must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for LinkedIn workspace operations with test conditions, baseline, observed range, and limitations. Success means conditions and measurements are reproducible, the comparison uses the stated budget, and limitations or resource costs are visible. The review is bounded to member or organization identity, profile scope, con...Votes: 0GitHub stars: 2
- Linkedin Automation Permission Boundary ReviewUse when LinkedIn workspace operations may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for LinkedIn workspace operations showing identity, requested capability, data scope, and approval gate. Success means every sensitive capability has a named authorization boundary, unnecessary data and privileges are called out, and no action is treated as approved by implication. The review is bounded to member or organization identity, profile...Votes: 0GitHub stars: 2
- Linkedin Automation Release Handoff RecordUse when a LinkedIn workspace operations review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for LinkedIn workspace operations with version, evidence, open issues, approval state, and safe next step. Success means the receiver can distinguish verified facts, proposals, approvals, and unknowns, and no publication, deployment, write, or contact is claimed unless independently confirmed. The review is bounded to member or organization identity, ...Votes: 0GitHub stars: 2
- Linkedin Automation Reproducibility Fixture PlanUse when a LinkedIn workspace operations result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for LinkedIn workspace operations defining fixture identity, environment, expected observations, and cleanup boundary. Success means another reviewer can identify the fixture and environment, distinguish expected from observed behavior, and repeat the check without an unapproved external effect. The review is bounded to membe...Votes: 0GitHub stars: 2
- Linkedin Automation Version CompatibilityUse when a LinkedIn workspace operations integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for LinkedIn workspace operations with exact versions, supported combinations, and open questions. Success means the tested version tuple is explicit, each compatibility claim has a dated source or local result, and unsupported combinations are not presented as working. The review is bounded to member or organization ident...Votes: 0GitHub stars: 2
- Loops ApiUse when a task involves integrating a backend with the Loops API or official SDK for contacts, events, lists, or transactional email to identify the intended outcome, relevant inputs, platform or version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive behavior, produce a reviewable artifact, and verify it against stated criteria. Trigger for planning, implementation, evaluation, or troubleshooting in this focused domain; do not ...Votes: 0GitHub stars: 2
- Loops CliUse when a task involves using the Loops CLI to inspect or prepare an approved email-marketing action to identify the intended outcome, relevant inputs, platform or version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive behavior, produce a reviewable artifact, and verify it against stated criteria. Trigger for planning, implementation, evaluation, or troubleshooting in this focused domain; do not install or run third-party comma...Votes: 0GitHub stars: 2
- Loops Email SendingUse when a task involves planning transactional or lifecycle email delivery through Loops with accurate event, consent, and idempotency behavior to identify the intended outcome, relevant inputs, platform or version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive behavior, produce a reviewable artifact, and verify it against stated criteria. Trigger for planning, implementation, evaluation, or troubleshooting in this focused doma...Votes: 0GitHub stars: 2
- Loops LmxUse when a task involves authoring or reviewing Loops LMX email markup against the user's content and rendering requirements to identify the intended outcome, relevant inputs, platform or version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive behavior, produce a reviewable artifact, and verify it against stated criteria. Trigger for planning, implementation, evaluation, or troubleshooting in this focused domain; do not install o...Votes: 0GitHub stars: 2
- Mailchimp Automation Capability Surface MapUse when the actual capability boundary of Mailchimp audience and campaign operations needs to be distinguished from assumptions. Produce a capability map for Mailchimp audience and campaign operations covering the requested behavior, verified support, exclusions, and unknowns. Success means each in-scope capability is tied to local configuration, a version-matched authoritative reference, or an observed non-production result, and all unknowns remain explicit. The review is bounded to audienc...Votes: 0GitHub stars: 2
- Mailchimp Automation Change Impact AssessmentUse when a proposed Mailchimp audience and campaign operations version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Mailchimp audience and campaign operations with baseline, affected dependencies, validation needs, and recovery boundary. Success means affected dependencies and compatibility assumptions are evidenced, unknown consumers are named as unknown, and no migration or rollout is implied. The review is bounded to audie...Votes: 0GitHub stars: 2
- Mailchimp Automation Failure Triage RecordUse when a reproducible Mailchimp audience and campaign operations symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Mailchimp audience and campaign operations with symptom, environment, evidence, hypothesis, and next safe check. Success means the diagnosis distinguishes observation from inference, each proposed check is reversible and scoped, and unresolved causes remain open. The review is bounded to audience identity, suppression rules, segme...Votes: 0GitHub stars: 2
- Mailchimp Automation Input Output ContractUse when the accepted inputs or produced outputs for Mailchimp audience and campaign operations need a checkable boundary. Produce an input/output contract for Mailchimp audience and campaign operations with types, required fields, exclusions, and representative approved fixtures. Success means the contract names its source and version, boundary cases are visible, and no private or unapproved payload is needed to explain the result. The review is bounded to audience identity, suppression rule...Votes: 0GitHub stars: 2