All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Gh Image Release Handoff RecordUse when a GitHub image attachment workflows review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for GitHub image attachment 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 image identity, local ass...Votes: 0GitHub stars: 2
- Gh Image Reproducibility Fixture PlanUse when a GitHub image attachment workflows result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for GitHub image attachment 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 ...Votes: 0GitHub stars: 2
- Gh Image Version CompatibilityUse when a GitHub image attachment workflows integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for GitHub image attachment 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 image identity, loca...Votes: 0GitHub stars: 2
- Git Implementation WorkflowUse when implementing a Git-compatible version-control subset or changing repository object, index, reference, branching, or history behavior to start with a disposable repository and a defined command subset; verify object identity and state transitions against Git where compatibility is claimed. Trigger for Git internals, clone-like tools, or version-control storage experiments.Votes: 0GitHub stars: 2
- Github Issue AuthoringUse when a task involves turning a verified problem or feature request into a concise, actionable GitHub issue 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-pa...Votes: 0GitHub stars: 2
- Github Mcp Read Only OperationsUse when a task involves using GitHub MCP tools to inspect repositories, issues, actions, or pull requests without modifying remote state to identify the intended outcome, affected account or artifact, exact product version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive details, produce a reviewable result, and verify it against explicit criteria. Trigger for planning, configuration, implementation, or troubleshooting in this fo...Votes: 0GitHub stars: 2
- Github Mcp Toolset ScopingUse when a task involves configuring GitHub's MCP server with only the repository toolsets and individual tools required for a task to identify the intended outcome, affected account or artifact, exact product version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive details, produce a reviewable result, and verify it against explicit criteria. Trigger for planning, configuration, implementation, or troubleshooting in this focused ...Votes: 0GitHub stars: 2
- Gitlab Commit Message WritingUse when a task involves writing commit messages that match a GitLab repository's existing convention and accurately describe a change to identify the intended outcome, affected account or artifact, exact product version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive details, produce a reviewable result, and verify it against explicit criteria. Trigger for planning, configuration, implementation, or troubleshooting in this focus...Votes: 0GitHub stars: 2
- Gitlab Glab Safe OperationsUse when a task involves using GitLab's glab CLI or API for an authorized project while avoiding shell-quoting and target-selection mistakes to identify the intended outcome, affected account or artifact, exact product version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive details, produce a reviewable result, and verify it against explicit criteria. Trigger for planning, configuration, implementation, or troubleshooting in this...Votes: 0GitHub stars: 2
- Gitlab Merge Request ReviewUse when a task involves reviewing a GitLab merge request for correctness, risk, test evidence, and readiness without taking over maintainer approval to identify the intended outcome, affected account or artifact, exact product version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive details, produce a reviewable result, and verify it against explicit criteria. Trigger for planning, configuration, implementation, or troubleshootin...Votes: 0GitHub stars: 2
- Gitlab Pipeline TriageUse when a task involves diagnosing a failed or stalled GitLab CI pipeline from job logs, artifacts, and recent configuration changes to identify the intended outcome, affected account or artifact, exact product version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive details, produce a reviewable result, and verify it against explicit criteria. Trigger for planning, configuration, implementation, or troubleshooting in this focuse...Votes: 0GitHub stars: 2
- Local Markdown Cross Reference Integrity LoopUse when a local edit changes file names, heading anchors, or reference paths to create or update a focused report of checked paths and minimal repairs. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: all scoped relative links resolve and point to the intended artifact. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible or irreversible writes.Votes: 0GitHub stars: 2
- Markdown Anchor Heading Change RepairUse when a document heading changes while local or external fragments may depend on it to create or update an inbound-link list with repaired anchors or redirect notes. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: all known in-scope references resolve to the intended section. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible or irreversible ...Votes: 0GitHub stars: 2
- Preview Deployment Source Build Parity CheckUse when a preview URL may have stale deployment state or a mismatched branch to create or update a preview parity record with requested commit, deployed identifier, and test URL. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: the deployment metadata and rendered result correspond to the reviewed source revision. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before...Votes: 0GitHub stars: 2
- Readme Command Instruction Replay CheckUse when a README or quickstart command may have drifted from the codebase to create or update a command-to-manifest mapping and safe replay result. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: the command exists, arguments match current tooling, and the bounded check succeeds. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible or irreversibl...Votes: 0GitHub stars: 2
- Repository Catalog Link Target SmokecheckUse when a repository index or generated catalog has been changed to create or update a link audit report with missing, duplicate, and misdirected targets. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: every catalog link resolves to one expected file and duplicate labels are explained. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible or irre...Votes: 0GitHub stars: 2
- Repository Claim To File Evidence ReconciliationUse when a status summary or technical answer includes claims about local code or configuration to create or update a claim ledger with repository path, location, and verification method. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: every local claim points to current evidence or is marked as an inference. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before exte...Votes: 0GitHub stars: 2
- Repository Visible Surface To Entrypoint MapUse when a repository must be investigated before selecting a file or running checks to create or update a read-only repository map with candidate entrypoints and unknowns. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: each proposed entrypoint is supported by a manifest, workflow, or referenced source file. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before exte...Votes: 0GitHub stars: 2
- Requirements Interview And SpecificationUse when a feature request is ambiguous, consequential, or large enough that different interpretations would produce materially different results to clarify user goals and constraints, ask only decision-changing questions, then write a compact, testable specification. Trigger before planning implementation when essential behavior, actors, scope, or acceptance conditions are missing.Votes: 0GitHub stars: 2
- Tokenwise Capability Surface MapUse when the actual capability boundary of Model-router measurement review needs to be distinguished from assumptions. Produce a capability map for Model-router measurement 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 task-class routing, provider ...Votes: 0GitHub stars: 2
- Tokenwise Change Impact AssessmentUse when a proposed Model-router measurement review version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Model-router measurement 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 task-class routing, provide...Votes: 0GitHub stars: 2
- Tokenwise Failure Triage RecordUse when a reproducible Model-router measurement review symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Model-router measurement 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 task-class routing, provider identity, usage metadata, budget att...Votes: 0GitHub stars: 2
- Tokenwise Input Output ContractUse when the accepted inputs or produced outputs for Model-router measurement review need a checkable boundary. Produce an input/output contract for Model-router measurement 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 task-class routing, provider identity, usage metadata, bu...Votes: 0GitHub stars: 2
- Tokenwise Integration Parity TraceUse when Model-router measurement review exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Model-router measurement 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 task-class routing, provider identity, usage metadata, budget attribution,...Votes: 0GitHub stars: 2
- Tokenwise Performance EnvelopeUse when Model-router measurement review must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Model-router measurement 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 task-class routing, provider identity, usage me...Votes: 0GitHub stars: 2
- Tokenwise Permission Boundary ReviewUse when Model-router measurement review may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Model-router measurement 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 task-class routing, provider identit...Votes: 0GitHub stars: 2
- Tokenwise Release Handoff RecordUse when a Model-router measurement review review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Model-router measurement 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 task-class routing, provider ...Votes: 0GitHub stars: 2
- Tokenwise Reproducibility Fixture PlanUse when a Model-router measurement review result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Model-router measurement 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. The review is bounded to t...Votes: 0GitHub stars: 2
- Tokenwise Version CompatibilityUse when a Model-router measurement review integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Model-router measurement 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 task-class routing, prov...Votes: 0GitHub stars: 2
- Uncategorized System BuildingUse when a build-from-scratch or systems-learning project does not fit an established domain skill, or its category is genuinely unclear to identify the artifact, research its authoritative interface, isolate risky assumptions, and deliver one demonstrable slice with explicit limitations. Trigger for novel project types, mixed-domain prototypes, or uncategorized tutorials.Votes: 0GitHub stars: 2
- Web Snippet To Fetched Source VerifierUse when a draft claim currently relies on a search snippet, preview, or summary card to create or update a claim ledger linking each statement to a fetched page location. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: the page contains the supporting passage with context and no omitted qualifier. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visi...Votes: 0GitHub stars: 2
- Aas Devtools Api Version Compat Approval Evidence PacketUse when a SDK API version compatibility result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the SDK compatibility 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; supported combinations are explicit and a migration path exists for each retired surface. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Aas Devtools Api Version Compat Change Impact TraceUse when a version, rule, source, or stakeholder change may affect SDK API version compatibility to produce a before/after change record and impact map for the SDK compatibility matrix. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; supported combinations are explicit and a migration path exists for each retired surface. Use configured search, fetch, read, browser, test, and write capabilities only when rele...Votes: 0GitHub stars: 2
- Aas Devtools Api Version Compat Closeout Handoff LedgerUse when a SDK API version compatibility work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the SDK compatibility 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; supported combinations are explicit and a migration path exists for each retired surface. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Aas Devtools Api Version Compat Completeness ReconciliationUse when the SDK API version compatibility workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the SDK compatibility 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; supported combinations are explicit and a migration path exists for each retired surface. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Aas Devtools Api Version Compat Exception Triage QueueUse when the SDK API version compatibility workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the SDK compatibility 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; supported combinations are explicit and a migration path exists for each retired surface. Use configured search, fetch, read, browser, test, and writ...Votes: 0GitHub stars: 2
- Aas Devtools Api Version Compat Recovery Readiness DrillUse when the SDK API version compatibility workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the SDK compatibility 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; supported combinations are explicit and a migration path exists for each retired surface. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Aas Devtools Api Version Compat Scenario Sensitivity MatrixUse when the SDK API version compatibility team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the SDK compatibility matrix with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; supported combinations are explicit and a migration path exists for each retired surface. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Aas Devtools Api Version Compat Scope Intake GateUse when a new SDK API version compatibility request needs a bounded work scope to produce a scoped intake card for the SDK compatibility matrix. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; supported combinations are explicit and a migration path exists for each retired surface. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to thr...Votes: 0GitHub stars: 2
- Aas Devtools Api Version Compat Source Provenance LedgerUse when a decision about SDK API version compatibility depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the SDK compatibility matrix. Success means each material claim has a source, version/date, location, and confidence note; supported combinations are explicit and a migration path exists for each retired surface. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evide...Votes: 0GitHub stars: 2
- Aas Devtools Api Version Compat Threshold Rule CheckUse when a SDK API version compatibility decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the SDK compatibility 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; supported combinations are explicit and a migration path exists for each retired surface. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Aas Devtools Sdk Error Contract Approval Evidence PacketUse when a SDK error and retry semantics result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the SDK error behavior table 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; callers can distinguish retryable from terminal errors without duplicate writes. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Aas Devtools Sdk Error Contract Change Impact TraceUse when a version, rule, source, or stakeholder change may affect SDK error and retry semantics to produce a before/after change record and impact map for the SDK error behavior table. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; callers can distinguish retryable from terminal errors without duplicate writes. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and ...Votes: 0GitHub stars: 2
- Aas Devtools Sdk Error Contract Closeout Handoff LedgerUse when a SDK error and retry semantics work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the SDK error behavior table 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; callers can distinguish retryable from terminal errors without duplicate writes. Use configured search, fetch, read, browser, test, and write capabili...Votes: 0GitHub stars: 2
- Aas Devtools Sdk Error Contract Completeness ReconciliationUse when the SDK error and retry semantics workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the SDK error behavior table 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; callers can distinguish retryable from terminal errors without duplicate writes. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Aas Devtools Sdk Error Contract Exception Triage QueueUse when the SDK error and retry semantics workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the SDK error behavior table 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; callers can distinguish retryable from terminal errors without duplicate writes. Use configured search, fetch, read, browser, test, and write capabil...Votes: 0GitHub stars: 2
- Aas Devtools Sdk Error Contract Recovery Readiness DrillUse when the SDK error and retry semantics workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the SDK error behavior table 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; callers can distinguish retryable from terminal errors without duplicate writes. Use configured search, fetch, read, browser, test, and wr...Votes: 0GitHub stars: 2
- Aas Devtools Sdk Error Contract Scenario Sensitivity MatrixUse when the SDK error and retry semantics team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the SDK error behavior table with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; callers can distinguish retryable from terminal errors without duplicate writes. Use configured search, fetch, read, browser, test, and write capabilities ...Votes: 0GitHub stars: 2
- Aas Devtools Sdk Error Contract Scope Intake GateUse when a new SDK error and retry semantics request needs a bounded work scope to produce a scoped intake card for the SDK error behavior table. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; callers can distinguish retryable from terminal errors without duplicate writes. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focuse...Votes: 0GitHub stars: 2
- Aas Devtools Sdk Error Contract Source Provenance LedgerUse when a decision about SDK error and retry semantics depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the SDK error behavior table. Success means each material claim has a source, version/date, location, and confidence note; callers can distinguish retryable from terminal errors without duplicate writes. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limi...Votes: 0GitHub stars: 2