All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Mailchimp Automation Integration Parity TraceUse when Mailchimp audience and campaign operations exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Mailchimp audience and campaign 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 audience identity, suppression rules, segment scope,...Votes: 0GitHub stars: 2
- Mailchimp Automation Performance EnvelopeUse when Mailchimp audience and campaign operations must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Mailchimp audience and campaign 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 audience identity, suppre...Votes: 0GitHub stars: 2
- Mailchimp Automation Permission Boundary ReviewUse when Mailchimp audience and campaign operations may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Mailchimp audience and campaign 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 audience ident...Votes: 0GitHub stars: 2
- Mailchimp Automation Release Handoff RecordUse when a Mailchimp audience and campaign operations review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Mailchimp audience and campaign 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 audienc...Votes: 0GitHub stars: 2
- Mailchimp Automation Reproducibility Fixture PlanUse when a Mailchimp audience and campaign operations result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Mailchimp audience and campaign 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 ...Votes: 0GitHub stars: 2
- Mailchimp Automation Version CompatibilityUse when a Mailchimp audience and campaign operations integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Mailchimp audience and campaign 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 au...Votes: 0GitHub stars: 2
- Marketing IdeasUse when a task involves generating and prioritizing practical marketing experiments from a defined growth goal and audience 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
- Marketing PsychologyUse when a task involves applying behavioral science to improve a marketing experience while preserving user understanding and choice 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
- Sales Enablement Capability Surface MapUse when the actual capability boundary of Sales enablement materials needs to be distinguished from assumptions. Produce a capability map for Sales enablement materials 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 approved product facts, audience, claim...Votes: 0GitHub stars: 2
- Sales Enablement Change Impact AssessmentUse when a proposed Sales enablement materials version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Sales enablement materials 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 approved product facts, audience, cla...Votes: 0GitHub stars: 2
- Sales Enablement Failure Triage RecordUse when a reproducible Sales enablement materials symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Sales enablement materials 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 approved product facts, audience, claim evidence, asset version, and public...Votes: 0GitHub stars: 2
- Sales Enablement Input Output ContractUse when the accepted inputs or produced outputs for Sales enablement materials need a checkable boundary. Produce an input/output contract for Sales enablement materials 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 approved product facts, audience, claim evidence, asset version, an...Votes: 0GitHub stars: 2
- Sales Enablement Integration Parity TraceUse when Sales enablement materials exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Sales enablement materials 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 approved product facts, audience, claim evidence, asset version, and publication app...Votes: 0GitHub stars: 2
- Sales Enablement Performance EnvelopeUse when Sales enablement materials must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Sales enablement materials 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 approved product facts, audience, claim evidence, asset v...Votes: 0GitHub stars: 2
- Sales Enablement Permission Boundary ReviewUse when Sales enablement materials may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Sales enablement materials 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 approved product facts, audience, claim eviden...Votes: 0GitHub stars: 2
- Sales Enablement Release Handoff RecordUse when a Sales enablement materials review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Sales enablement materials 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 approved product facts, audience, claim...Votes: 0GitHub stars: 2
- Sales Enablement Reproducibility Fixture PlanUse when a Sales enablement materials result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Sales enablement materials 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 approved pr...Votes: 0GitHub stars: 2
- Sales Enablement Version CompatibilityUse when a Sales enablement materials integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Sales enablement materials 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 approved product facts, audience, ...Votes: 0GitHub stars: 2
- Seo AuditUse when a task involves auditing a website's technical and content discoverability with a defined crawl scope and evidence-backed recommendations 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 do...Votes: 0GitHub stars: 2
- Seo Hreflang Capability Surface MapUse when the actual capability boundary of International SEO language-region mapping needs to be distinguished from assumptions. Produce a capability map for International SEO language-region mapping 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 locale in...Votes: 0GitHub stars: 2
- Seo Hreflang Change Impact AssessmentUse when a proposed International SEO language-region mapping version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for International SEO language-region mapping 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 locale ...Votes: 0GitHub stars: 2
- Seo Hreflang Failure Triage RecordUse when a reproducible International SEO language-region mapping symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for International SEO language-region mapping 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 locale inventory, canonical identity, recipro...Votes: 0GitHub stars: 2
- Seo Hreflang Input Output ContractUse when the accepted inputs or produced outputs for International SEO language-region mapping need a checkable boundary. Produce an input/output contract for International SEO language-region mapping 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 locale inventory, canonical identity,...Votes: 0GitHub stars: 2
- Seo Hreflang Integration Parity TraceUse when International SEO language-region mapping exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for International SEO language-region mapping 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 locale inventory, canonical identity, reciprocal links...Votes: 0GitHub stars: 2
- Seo Hreflang Performance EnvelopeUse when International SEO language-region mapping must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for International SEO language-region mapping 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 locale inventory, canonical...Votes: 0GitHub stars: 2
- Seo Hreflang Permission Boundary ReviewUse when International SEO language-region mapping may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for International SEO language-region mapping 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 locale inventory...Votes: 0GitHub stars: 2
- Seo Hreflang Release Handoff RecordUse when a International SEO language-region mapping review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for International SEO language-region mapping 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 locale in...Votes: 0GitHub stars: 2
- Seo Hreflang Reproducibility Fixture PlanUse when a International SEO language-region mapping result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for International SEO language-region mapping 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 re...Votes: 0GitHub stars: 2
- Seo Hreflang Version CompatibilityUse when a International SEO language-region mapping integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for International SEO language-region mapping 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 loca...Votes: 0GitHub stars: 2
- Seo Images Capability Surface MapUse when the actual capability boundary of Image-related search and performance review needs to be distinguished from assumptions. Produce a capability map for Image-related search and performance review 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 asset...Votes: 0GitHub stars: 2
- Seo Images Change Impact AssessmentUse when a proposed Image-related search and performance review version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Image-related search and performance review 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 ass...Votes: 0GitHub stars: 2
- Seo Images Failure Triage RecordUse when a reproducible Image-related search and performance review symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Image-related search and performance review 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 asset identity, descriptive text, dimensi...Votes: 0GitHub stars: 2
- Seo Images Input Output ContractUse when the accepted inputs or produced outputs for Image-related search and performance review need a checkable boundary. Produce an input/output contract for Image-related search and performance review 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 asset identity, descriptive text,...Votes: 0GitHub stars: 2
- Seo Images Integration Parity TraceUse when Image-related search and performance review exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Image-related search and performance review 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 asset identity, descriptive text, dimensions, form...Votes: 0GitHub stars: 2
- Seo Images Performance EnvelopeUse when Image-related search and performance review must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Image-related search and performance review 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 asset identity, descrip...Votes: 0GitHub stars: 2
- Seo Images Permission Boundary ReviewUse when Image-related search and performance review may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Image-related search and performance review 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 asset identi...Votes: 0GitHub stars: 2
- Seo Images Release Handoff RecordUse when a Image-related search and performance review review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Image-related search and performance review 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 asset...Votes: 0GitHub stars: 2
- Seo Images Reproducibility Fixture PlanUse when a Image-related search and performance review result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Image-related search and performance review 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. Th...Votes: 0GitHub stars: 2
- Seo Images Version CompatibilityUse when a Image-related search and performance review integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Image-related search and performance review 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 ...Votes: 0GitHub stars: 2
- Seo Programmatic Capability Surface MapUse when the actual capability boundary of Programmatic SEO page systems needs to be distinguished from assumptions. Produce a capability map for Programmatic SEO page systems 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 template identity, source-data qu...Votes: 0GitHub stars: 2
- Seo Programmatic Change Impact AssessmentUse when a proposed Programmatic SEO page systems version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Programmatic SEO page systems 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 template identity, source-data ...Votes: 0GitHub stars: 2
- Seo Programmatic Failure Triage RecordUse when a reproducible Programmatic SEO page systems symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Programmatic SEO page systems 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 template identity, source-data quality, duplicate risk, internal link...Votes: 0GitHub stars: 2
- Seo Programmatic Input Output ContractUse when the accepted inputs or produced outputs for Programmatic SEO page systems need a checkable boundary. Produce an input/output contract for Programmatic SEO page systems 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 template identity, source-data quality, duplicate risk, inter...Votes: 0GitHub stars: 2
- Seo Programmatic Integration Parity TraceUse when Programmatic SEO page systems exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Programmatic SEO page systems 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 template identity, source-data quality, duplicate risk, internal links, and in...Votes: 0GitHub stars: 2
- Seo Programmatic Performance EnvelopeUse when Programmatic SEO page systems must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Programmatic SEO page systems 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 template identity, source-data quality, duplicate r...Votes: 0GitHub stars: 2
- Seo Programmatic Permission Boundary ReviewUse when Programmatic SEO page systems may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Programmatic SEO page systems 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 template identity, source-data quality, ...Votes: 0GitHub stars: 2
- Seo Programmatic Release Handoff RecordUse when a Programmatic SEO page systems review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Programmatic SEO page systems 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 template identity, source-data qu...Votes: 0GitHub stars: 2
- Seo Programmatic Reproducibility Fixture PlanUse when a Programmatic SEO page systems result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Programmatic SEO page systems 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 templ...Votes: 0GitHub stars: 2
- Seo Programmatic Version CompatibilityUse when a Programmatic SEO page systems integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Programmatic SEO page systems 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 template identity, source-da...Votes: 0GitHub stars: 2
- Telegram Bot Messaging Capability Surface MapUse when the actual capability boundary of Telegram bot messaging needs to be distinguished from assumptions. Produce a capability map for Telegram bot messaging 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 bot and chat identity, message preview, callbac...Votes: 0GitHub stars: 2