All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Telegram Bot Messaging Change Impact AssessmentUse when a proposed Telegram bot messaging version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Telegram bot messaging 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 bot and chat identity, message preview, callb...Votes: 0GitHub stars: 2
- Telegram Bot Messaging Failure Triage RecordUse when a reproducible Telegram bot messaging symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Telegram bot messaging 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 bot and chat identity, message preview, callback state, rate limits, and send autho...Votes: 0GitHub stars: 2
- Telegram Bot Messaging Input Output ContractUse when the accepted inputs or produced outputs for Telegram bot messaging need a checkable boundary. Produce an input/output contract for Telegram bot messaging 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 bot and chat identity, message preview, callback state, rate limits, and se...Votes: 0GitHub stars: 2
- Telegram Bot Messaging Integration Parity TraceUse when Telegram bot messaging exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Telegram bot messaging 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 bot and chat identity, message preview, callback state, rate limits, and send authorization....Votes: 0GitHub stars: 2
- Telegram Bot Messaging Performance EnvelopeUse when Telegram bot messaging must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Telegram bot messaging 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 bot and chat identity, message preview, callback state, rate limi...Votes: 0GitHub stars: 2
- Telegram Bot Messaging Permission Boundary ReviewUse when Telegram bot messaging may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Telegram bot messaging 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 bot and chat identity, message preview, callback state...Votes: 0GitHub stars: 2
- Telegram Bot Messaging Release Handoff RecordUse when a Telegram bot messaging review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Telegram bot messaging 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 bot and chat identity, message preview, callbac...Votes: 0GitHub stars: 2
- Telegram Bot Messaging Reproducibility Fixture PlanUse when a Telegram bot messaging result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Telegram bot messaging 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 bot and chat identi...Votes: 0GitHub stars: 2
- Telegram Bot Messaging Version CompatibilityUse when a Telegram bot messaging integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Telegram bot messaging 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 bot and chat identity, message preview, ca...Votes: 0GitHub stars: 2
- Zendesk Automation Capability Surface MapUse when the actual capability boundary of Zendesk ticket workflows needs to be distinguished from assumptions. Produce a capability map for Zendesk ticket 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 and requester identity, comment visi...Votes: 0GitHub stars: 2
- Zendesk Automation Change Impact AssessmentUse when a proposed Zendesk ticket workflows version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Zendesk ticket 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 and requester identity, comment vi...Votes: 0GitHub stars: 2
- Zendesk Automation Failure Triage RecordUse when a reproducible Zendesk ticket workflows symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Zendesk ticket 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 and requester identity, comment visibility, status transitions, and noti...Votes: 0GitHub stars: 2
- Zendesk Automation Input Output ContractUse when the accepted inputs or produced outputs for Zendesk ticket workflows need a checkable boundary. Produce an input/output contract for Zendesk ticket 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 and requester identity, comment visibility, status transitions, ...Votes: 0GitHub stars: 2
- Zendesk Automation Integration Parity TraceUse when Zendesk ticket workflows exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Zendesk ticket 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 and requester identity, comment visibility, status transitions, and notification ...Votes: 0GitHub stars: 2
- Zendesk Automation Performance EnvelopeUse when Zendesk ticket workflows must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Zendesk ticket 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 and requester identity, comment visibility, status tra...Votes: 0GitHub stars: 2
- Zendesk Automation Permission Boundary ReviewUse when Zendesk ticket workflows may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Zendesk ticket 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 and requester identity, comment visibility,...Votes: 0GitHub stars: 2
- Zendesk Automation Release Handoff RecordUse when a Zendesk ticket workflows review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Zendesk ticket 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 and requester identity, comment visi...Votes: 0GitHub stars: 2
- Zendesk Automation Reproducibility Fixture PlanUse when a Zendesk ticket workflows result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Zendesk ticket 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 ticket and requ...Votes: 0GitHub stars: 2
- Zendesk Automation Version CompatibilityUse when a Zendesk ticket workflows integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Zendesk ticket 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 and requester identity, comment...Votes: 0GitHub stars: 2
- Onboarding Conversion OptimizationUse when a task involves improving a product onboarding flow by reducing friction and helping users reach a verified first-value moment 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 no...Votes: 0GitHub stars: 2
- People Ops Benefits Admin Approval Evidence PacketUse when a benefits and payroll administration result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the benefits administration exception list 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; no individual eligibility or tax conclusion is made without the authorized administrator. Use configured se...Votes: 0GitHub stars: 2
- People Ops Benefits Admin Change Impact TraceUse when a version, rule, source, or stakeholder change may affect benefits and payroll administration to produce a before/after change record and impact map for the benefits administration exception list. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; no individual eligibility or tax conclusion is made without the authorized administrator. Use configured search, fetch, read, browser, test, and write capabil...Votes: 0GitHub stars: 2
- People Ops Benefits Admin Closeout Handoff LedgerUse when a benefits and payroll administration work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the benefits administration exception list 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; no individual eligibility or tax conclusion is made without the authorized administrator. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- People Ops Benefits Admin Completeness ReconciliationUse when the benefits and payroll administration workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the benefits administration exception list 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; no individual eligibility or tax conclusion is made without the authorized administrator. Use configured search, fet...Votes: 0GitHub stars: 2
- People Ops Benefits Admin Exception Triage QueueUse when the benefits and payroll administration workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the benefits administration exception list 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; no individual eligibility or tax conclusion is made without the authorized administrator. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- People Ops Benefits Admin Recovery Readiness DrillUse when the benefits and payroll administration workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the benefits administration exception list 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; no individual eligibility or tax conclusion is made without the authorized administrator. Use configured search, fetch...Votes: 0GitHub stars: 2
- People Ops Benefits Admin Scenario Sensitivity MatrixUse when the benefits and payroll administration team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the benefits administration exception list with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; no individual eligibility or tax conclusion is made without the authorized administrator. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- People Ops Benefits Admin Scope Intake GateUse when a new benefits and payroll administration request needs a bounded work scope to produce a scoped intake card for the benefits administration exception list. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; no individual eligibility or tax conclusion is made without the authorized administrator. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, lim...Votes: 0GitHub stars: 2
- People Ops Benefits Admin Source Provenance LedgerUse when a decision about benefits and payroll administration depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the benefits administration exception list. Success means each material claim has a source, version/date, location, and confidence note; no individual eligibility or tax conclusion is made without the authorized administrator. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and auth...Votes: 0GitHub stars: 2
- People Ops Benefits Admin Threshold Rule CheckUse when a benefits and payroll administration decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the benefits administration exception list 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; no individual eligibility or tax conclusion is made without the authorized administrator. Use configured searc...Votes: 0GitHub stars: 2
- People Ops Employee Relations Approval Evidence PacketUse when a employee-relations intake and routing result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the confidential employee-relations intake log 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; allegations are recorded neutrally, no credibility or guilt judgment is generated, and urgent safety ...Votes: 0GitHub stars: 2
- People Ops Employee Relations Change Impact TraceUse when a version, rule, source, or stakeholder change may affect employee-relations intake and routing to produce a before/after change record and impact map for the confidential employee-relations intake log. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; allegations are recorded neutrally, no credibility or guilt judgment is generated, and urgent safety concerns are escalated. Use configured search, fetc...Votes: 0GitHub stars: 2
- People Ops Employee Relations Closeout Handoff LedgerUse when a employee-relations intake and routing work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the confidential employee-relations intake log 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; allegations are recorded neutrally, no credibility or guilt judgment is generated, and urgent safety concerns are escalated....Votes: 0GitHub stars: 2
- People Ops Employee Relations Completeness ReconciliationUse when the employee-relations intake and routing workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the confidential employee-relations intake log 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; allegations are recorded neutrally, no credibility or guilt judgment is generated, and urgent safety concerns ...Votes: 0GitHub stars: 2
- People Ops Employee Relations Exception Triage QueueUse when the employee-relations intake and routing workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the confidential employee-relations intake log 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; allegations are recorded neutrally, no credibility or guilt judgment is generated, and urgent safety concerns are escalated...Votes: 0GitHub stars: 2
- People Ops Employee Relations Recovery Readiness DrillUse when the employee-relations intake and routing workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the confidential employee-relations intake log 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; allegations are recorded neutrally, no credibility or guilt judgment is generated, and urgent safety concerns ar...Votes: 0GitHub stars: 2
- People Ops Employee Relations Scenario Sensitivity MatrixUse when the employee-relations intake and routing team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the confidential employee-relations intake log with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; allegations are recorded neutrally, no credibility or guilt judgment is generated, and urgent safety concerns are escalated. Use ...Votes: 0GitHub stars: 2
- People Ops Employee Relations Scope Intake GateUse when a new employee-relations intake and routing request needs a bounded work scope to produce a scoped intake card for the confidential employee-relations intake log. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; allegations are recorded neutrally, no credibility or guilt judgment is generated, and urgent safety concerns are escalated. Use configured search, fetch, read, browser, test, and write capabilities only when rele...Votes: 0GitHub stars: 2
- People Ops Employee Relations Source Provenance LedgerUse when a decision about employee-relations intake and routing depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the confidential employee-relations intake log. Success means each material claim has a source, version/date, location, and confidence note; allegations are recorded neutrally, no credibility or guilt judgment is generated, and urgent safety concerns are escalated. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- People Ops Employee Relations Threshold Rule CheckUse when a employee-relations intake and routing decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the confidential employee-relations intake log 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; allegations are recorded neutrally, no credibility or guilt judgment is generated, and urgent safety con...Votes: 0GitHub stars: 2
- People Ops Learning Approval Evidence PacketUse when a workforce learning and credential tracking result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the learning requirement 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; completion status maps to the current requirement and exceptions are not treated as misconduct. Use configured ...Votes: 0GitHub stars: 2
- People Ops Learning Change Impact TraceUse when a version, rule, source, or stakeholder change may affect workforce learning and credential tracking to produce a before/after change record and impact map for the learning requirement matrix. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; completion status maps to the current requirement and exceptions are not treated as misconduct. Use configured search, fetch, read, browser, test, and write capab...Votes: 0GitHub stars: 2
- People Ops Learning Closeout Handoff LedgerUse when a workforce learning and credential tracking work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the learning requirement 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; completion status maps to the current requirement and exceptions are not treated as misconduct. Use configured search, fetch, read, br...Votes: 0GitHub stars: 2
- People Ops Learning Completeness ReconciliationUse when the workforce learning and credential tracking workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the learning requirement 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; completion status maps to the current requirement and exceptions are not treated as misconduct. Use configured search, f...Votes: 0GitHub stars: 2
- People Ops Learning Exception Triage QueueUse when the workforce learning and credential tracking workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the learning requirement 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; completion status maps to the current requirement and exceptions are not treated as misconduct. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- People Ops Learning Recovery Readiness DrillUse when the workforce learning and credential tracking workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the learning requirement 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; completion status maps to the current requirement and exceptions are not treated as misconduct. Use configured search, fet...Votes: 0GitHub stars: 2
- People Ops Learning Scenario Sensitivity MatrixUse when the workforce learning and credential tracking team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the learning requirement matrix with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; completion status maps to the current requirement and exceptions are not treated as misconduct. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- People Ops Learning Scope Intake GateUse when a new workforce learning and credential tracking request needs a bounded work scope to produce a scoped intake card for the learning requirement matrix. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; completion status maps to the current requirement and exceptions are not treated as misconduct. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, l...Votes: 0GitHub stars: 2
- People Ops Learning Source Provenance LedgerUse when a decision about workforce learning and credential tracking depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the learning requirement matrix. Success means each material claim has a source, version/date, location, and confidence note; completion status maps to the current requirement and exceptions are not treated as misconduct. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and au...Votes: 0GitHub stars: 2
- People Ops Learning Threshold Rule CheckUse when a workforce learning and credential tracking decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the learning requirement 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; completion status maps to the current requirement and exceptions are not treated as misconduct. Use configured sea...Votes: 0GitHub stars: 2