egorfedorov/slot-casino-game-developer-skills-for-stake-engine

provider-integration

Integrate external/internal providers through stable adapter contracts and resilience controls. Use when adding or auditing provider APIs, normalizing data contracts, defining fallback behavior, or validating provider integration readiness before release.

First seen Mar 10, 2026

Installation

$ npx skills add egorfedorov/slot-casino-game-developer-skills-for-stake-engine --skill provider-integration

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from egorfedorov/slot-casino-game-developer-skills-for-stake-engine · top by installs.

npx skills add egorfedorov/slot-casino-game-developer-skills-for-stake-engine

Browse all from egorfedorov/slot-casino-game-developer-skills-for-stake-engine

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 53
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,713 B
  • docs SUMMARY.md 283 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 14 installs

SKILL.md

Provider Integration

Use this skill to implement provider integrations with strict contract and fallback behavior.

Workflow

  1. Define scope and constraints.
  • Define provider contract, auth model, rate limits, and error taxonomy.
  • Capture objective metrics, bounds, and release blockers.
  1. Design implementation plan.
  • Design adapter boundaries and schema normalization rules.
  • Keep ownership and dependency boundaries explicit.
  1. Execute and iterate.
  • Implement in small, traceable increments.
  • Record run/build context for reproducibility.
  1. Validate contract integrity.
  • Validate contract compliance, retry/fallback behavior, and observability.
  • Treat contract breaches as blockers.
  1. Prepare handoff.
  • Deliver adapter patch plan, migration notes, and verification steps.
  • Include exact commands and acceptance criteria.

Output Contract

Return:

  1. Context: goals, assumptions, constraints.
  2. Validation: pass/fail checks and key deltas.
  3. Changes: concrete file-level updates.
  4. Commands: commands and expected outputs.
  5. Risks: unresolved issues and limits.

References

  • references/workflow.md: detailed execution flow.
  • references/checklist.md: sign-off checklist.

Execution Rules

  • Keep decisions measurable and reversible.
  • Keep validation criteria explicit before iteration.
  • Treat schema drift and unhandled provider errors as blockers.