All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Aas Devrel Tutorial Prerequisites Threshold Rule CheckUse when a technical tutorial prerequisite accuracy decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the tutorial prerequisite verification sheet showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; the prerequisite list is sufficient for the described first result in a fresh test. Use configured sear...Votes: 0GitHub stars: 2
- Community MarketingUse when a task involves designing a community program that provides member value and supports a measurable, consent-respecting business goal 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;...Votes: 0GitHub stars: 2
- Freshservice Automation Capability Surface MapUse when the actual capability boundary of Freshservice service workflows needs to be distinguished from assumptions. Produce a capability map for Freshservice service workflows 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 ticket identity, requester fiel...Votes: 0GitHub stars: 2
- Freshservice Automation Change Impact AssessmentUse when a proposed Freshservice service workflows version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Freshservice service workflows 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 ticket identity, requester fi...Votes: 0GitHub stars: 2
- Freshservice Automation Failure Triage RecordUse when a reproducible Freshservice service workflows symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Freshservice service workflows 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 ticket identity, requester fields, state transitions, service reque...Votes: 0GitHub stars: 2
- Freshservice Automation Input Output ContractUse when the accepted inputs or produced outputs for Freshservice service workflows need a checkable boundary. Produce an input/output contract for Freshservice service workflows 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 ticket identity, requester fields, state transitions, servi...Votes: 0GitHub stars: 2
- Freshservice Automation Integration Parity TraceUse when Freshservice service workflows exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Freshservice service workflows 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 ticket identity, requester fields, state transitions, service requests, and ...Votes: 0GitHub stars: 2
- Freshservice Automation Performance EnvelopeUse when Freshservice service workflows must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Freshservice service workflows 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 ticket identity, requester fields, state transiti...Votes: 0GitHub stars: 2
- Freshservice Automation Permission Boundary ReviewUse when Freshservice service workflows may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Freshservice service workflows 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 ticket identity, requester fields, sta...Votes: 0GitHub stars: 2
- Freshservice Automation Release Handoff RecordUse when a Freshservice service workflows review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Freshservice service workflows 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 ticket identity, requester fiel...Votes: 0GitHub stars: 2
- Freshservice Automation Reproducibility Fixture PlanUse when a Freshservice service workflows result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Freshservice service workflows 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 tic...Votes: 0GitHub stars: 2
- Freshservice Automation Version CompatibilityUse when a Freshservice service workflows integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Freshservice service workflows 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 ticket identity, requester...Votes: 0GitHub stars: 2
- Gtm Ops Account Research Approval Evidence PacketUse when a account research result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the account context 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; each material claim has a source and uncertainty is stated. Use configured search, fetch, read, browser, test, and write capabilities only when...Votes: 0GitHub stars: 2
- Gtm Ops Account Research Change Impact TraceUse when a version, rule, source, or stakeholder change may affect account research to produce a before/after change record and impact map for the account context brief. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each material claim has a source and uncertainty is stated. 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 Account Research Closeout Handoff LedgerUse when a account research work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the account context 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; each material claim has a source and uncertainty is stated. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorize...Votes: 0GitHub stars: 2
- Gtm Ops Account Research Completeness ReconciliationUse when the account research workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the account context 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; each material claim has a source and uncertainty is stated. Use configured search, fetch, read, browser, test, and write capabilities only when relevant...Votes: 0GitHub stars: 2
- Gtm Ops Account Research Exception Triage QueueUse when the account research workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the account context 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; each material claim has a source and uncertainty is stated. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authoriz...Votes: 0GitHub stars: 2
- Gtm Ops Account Research Recovery Readiness DrillUse when the account research workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the account context 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; each material claim has a source and uncertainty is stated. Use configured search, fetch, read, browser, test, and write capabilities only when relevant a...Votes: 0GitHub stars: 2
- Gtm Ops Account Research Scenario Sensitivity MatrixUse when the account research team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the account context brief with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each material claim has a source and uncertainty is stated. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Re...Votes: 0GitHub stars: 2
- Gtm Ops Account Research Scope Intake GateUse when a new account research request needs a bounded work scope to produce a scoped intake card for the account context brief. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each material claim has a source and uncertainty is stated. 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 approval before ex...Votes: 0GitHub stars: 2
- Gtm Ops Account Research Source Provenance LedgerUse when a decision about account research depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the account context brief. Success means each material claim has a source, version/date, location, and confidence note; each material claim has a source and uncertainty is stated. 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 Account Research Threshold Rule CheckUse when a account research decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the account context 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; each material claim has a source and uncertainty is stated. Use configured search, fetch, read, browser, test, and write capabilities only when re...Votes: 0GitHub stars: 2
- Gtm Ops Adoption Approval Evidence PacketUse when a product adoption health result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the adoption evidence 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; usage claims use a stable cohort and distinguish product activity from customer value. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Gtm Ops Adoption Change Impact TraceUse when a version, rule, source, or stakeholder change may affect product adoption health to produce a before/after change record and impact map for the adoption evidence brief. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; usage claims use a stable cohort and distinguish product activity from customer value. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and a...Votes: 0GitHub stars: 2
- Gtm Ops Adoption Closeout Handoff LedgerUse when a product adoption health work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the adoption evidence 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; usage claims use a stable cohort and distinguish product activity from customer value. Use configured search, fetch, read, browser, test, and write capabilit...Votes: 0GitHub stars: 2
- Gtm Ops Adoption Completeness ReconciliationUse when the product adoption health workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the adoption 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; usage claims use a stable cohort and distinguish product activity from customer value. Use configured search, fetch, read, browser, test, and w...Votes: 0GitHub stars: 2
- Gtm Ops Adoption Exception Triage QueueUse when the product adoption health workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the adoption 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; usage claims use a stable cohort and distinguish product activity from customer value. Use configured search, fetch, read, browser, test, and write capabili...Votes: 0GitHub stars: 2
- Gtm Ops Adoption Recovery Readiness DrillUse when the product adoption health workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the adoption 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; usage claims use a stable cohort and distinguish product activity from customer value. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Gtm Ops Adoption Scenario Sensitivity MatrixUse when the product adoption health team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the adoption evidence brief with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; usage claims use a stable cohort and distinguish product activity from customer value. Use configured search, fetch, read, browser, test, and write capabilities o...Votes: 0GitHub stars: 2
- Gtm Ops Adoption Scope Intake GateUse when a new product adoption health request needs a bounded work scope to produce a scoped intake card for the adoption evidence brief. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; usage claims use a stable cohort and distinguish product activity from customer value. 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
- Gtm Ops Adoption Source Provenance LedgerUse when a decision about product adoption health depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the adoption evidence brief. Success means each material claim has a source, version/date, location, and confidence note; usage claims use a stable cohort and distinguish product activity from customer value. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit...Votes: 0GitHub stars: 2
- Gtm Ops Adoption Threshold Rule CheckUse when a product adoption health decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the adoption 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; usage claims use a stable cohort and distinguish product activity from customer value. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Gtm Ops Campaigns Approval Evidence PacketUse when a campaign operations result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the campaign QA 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; all segments and links pass review and no suppressed recipient is included. Use configured search, fetch, read, browser, test, and write capabi...Votes: 0GitHub stars: 2
- Gtm Ops Campaigns Change Impact TraceUse when a version, rule, source, or stakeholder change may affect campaign operations to produce a before/after change record and impact map for the campaign QA packet. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; all segments and links pass review and no suppressed recipient is included. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record ev...Votes: 0GitHub stars: 2
- Gtm Ops Campaigns Closeout Handoff LedgerUse when a campaign operations work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the campaign QA 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; all segments and links pass review and no suppressed recipient is included. Use configured search, fetch, read, browser, test, and write capabilities only when releva...Votes: 0GitHub stars: 2
- Gtm Ops Campaigns Completeness ReconciliationUse when the campaign operations workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the campaign QA 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; all segments and links pass review and no suppressed recipient is included. Use configured search, fetch, read, browser, test, and write capabilities on...Votes: 0GitHub stars: 2
- Gtm Ops Campaigns Exception Triage QueueUse when the campaign operations workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the campaign QA 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; all segments and links pass review and no suppressed recipient is included. Use configured search, fetch, read, browser, test, and write capabilities only when relev...Votes: 0GitHub stars: 2
- Gtm Ops Campaigns Recovery Readiness DrillUse when the campaign operations workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the campaign QA 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; all segments and links pass review and no suppressed recipient is included. Use configured search, fetch, read, browser, test, and write capabilities only...Votes: 0GitHub stars: 2
- Gtm Ops Campaigns Scenario Sensitivity MatrixUse when the campaign operations team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the campaign QA packet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; all segments and links pass review and no suppressed recipient is included. Use configured search, fetch, read, browser, test, and write capabilities only when relevant an...Votes: 0GitHub stars: 2
- Gtm Ops Campaigns Scope Intake GateUse when a new campaign operations request needs a bounded work scope to produce a scoped intake card for the campaign QA packet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; all segments and links pass review and no suppressed recipient is included. 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 ap...Votes: 0GitHub stars: 2
- Gtm Ops Campaigns Source Provenance LedgerUse when a decision about campaign operations depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the campaign QA packet. Success means each material claim has a source, version/date, location, and confidence note; all segments and links pass review and no suppressed recipient is included. 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 Campaigns Threshold Rule CheckUse when a campaign operations decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the campaign QA 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; all segments and links pass review and no suppressed recipient is included. Use configured search, fetch, read, browser, test, and write capabilit...Votes: 0GitHub stars: 2
- Gtm Ops Content Approval Evidence PacketUse when a commercial content governance result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the claim-source 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; every objective claim is current, sourced, and approved for the intended channel. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Gtm Ops Content Change Impact TraceUse when a version, rule, source, or stakeholder change may affect commercial content governance to produce a before/after change record and impact map for the claim-source matrix. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; 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 auth...Votes: 0GitHub stars: 2
- Gtm Ops Content Closeout Handoff LedgerUse when a commercial content governance work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the claim-source 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; every objective claim is current, sourced, and approved for the intended channel. Use configured search, fetch, read, browser, test, and write capabilities...Votes: 0GitHub stars: 2
- Gtm Ops Content Completeness ReconciliationUse when the commercial content governance workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the claim-source 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; every objective claim is current, sourced, and approved for the intended channel. Use configured search, fetch, read, browser, test, and writ...Votes: 0GitHub stars: 2
- Gtm Ops Content Exception Triage QueueUse when the commercial content governance workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the claim-source 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; every objective claim is current, sourced, and approved for the intended channel. Use configured search, fetch, read, browser, test, and write capabilitie...Votes: 0GitHub stars: 2
- Gtm Ops Content Recovery Readiness DrillUse when the commercial content governance workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the claim-source 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; every objective claim is current, sourced, and approved for the intended channel. Use configured search, fetch, read, browser, test, and write ...Votes: 0GitHub stars: 2
- Gtm Ops Content Scenario Sensitivity MatrixUse when the commercial content governance team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the claim-source matrix with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; every objective claim is current, sourced, and approved for the intended channel. Use configured search, fetch, read, browser, test, and write capabilities only...Votes: 0GitHub stars: 2
- Gtm Ops Content Scope Intake GateUse when a new commercial content governance request needs a bounded work scope to produce a scoped intake card for the claim-source matrix. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; 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 refinement to three focused pa...Votes: 0GitHub stars: 2