fluxly Search skills… ⌘K 中文 Publish

spinngo-databingo

Data Community
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
Data
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
88 / 100 · community maintained
Author / version / license
@tobias363 · no license declared
Token usage
Heavy
Setup complexity
Manual integration
External API key
Not required
Operating systems
Docker
Runtime requirements
Docker
Permissions
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview spinngo-databingo.preview 
---
name: spinngo-databingo
description: When the user/agent works with SpinnGo (Spill 4 / game5 / spillorama-slug), databingo classifica…
category: data
runtime: Docker
---

# spinngo-databingo output preview

## PART A: Task fit
- Use case: When the user/agent works with SpinnGo (Spill 4 / game5 / spillorama-slug), databingo classification, the 30%-til-organisasjoner-regel, the 2500 kr single-prize-cap, or legacy Unity SpinnGo's 3×3 / 1-36 / 14-draw pattern game with roulette/bonus. Also use when they mention game5, spillorama-slug, SpinnGo, Spill 4, databingo, databingo system, ruletthjul, single-prize-cap, 3x3-grid, 1-36, 14 trekk, pattern multipliers, bonusTrigger, WOF, roulette settings, ledgerGameTypeForSlug, makeHouseAccountId, themebingo deprecated, BIN-496, ComplianceLedgerOverskudd, §11 distribusjon, forhåndstrukket, player-startet. Make sure to use this skill whenever someone touches SpinnGo, databingo-paths, eller forveksler regulatorisk klassifisering mellom hovedspill og databingo — even if they don't explicitly ask for it..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “📚 Tier 1 context — load when skill activates / Kontekst — hvorfor er dette kritisk? / Mapping-tabell — markedsføring vs kodenavn vs slug” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “When the user/agent works with SpinnGo (Spill 4 / game5 / spillorama-slug), databingo classification, the 30%-til-organisasjoner-regel, the 2500 kr single-prize-cap, or legacy Unity SpinnGo's 3×3 / 1-36 / 14-draw pattern game with roulette/bonus. Also use when they mention game5, spillorama-slug, SpinnGo, Spill 4, databingo, databingo system, ruletthjul, single-prize-cap, 3x3-grid, 1-36, 14 trekk, pattern multipliers, bonusTrigger, WOF, roulette settings, ledgerGameTypeForSlug, makeHouseAccountId, themebingo deprecated, BIN-496, ComplianceLedgerOverskudd, §11 distribusjon, forhåndstrukket, player-startet. Make sure to use this skill whenever someone touches SpinnGo, databingo-paths, eller forveksler regulatorisk klassifisering mellom hovedspill og databingo — even if they don't explicitly ask for it.”.
- **02** When the source has headings, the agent prioritizes “📚 Tier 1 context — load when skill activates / Kontekst — hvorfor er dette kritisk? / Mapping-tabell — markedsføring vs kodenavn vs slug” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.
Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

  • Core job: When the user/agent works with SpinnGo (Spill 4 / game5 / spillorama-slug), databingo classification, the 30%-til-organisasjoner…
  • Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
  • Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

  • Structure: The skill is organized around “📚 Tier 1 context — load when skill activates”, “Kontekst — hvorfor er dette kritisk?”, “Mapping-tabell — markedsføring vs kodenavn vs slug”, “Kanonisk SpinnGo alias-set (PR 1715, 2026-05-23)”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
  • Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
  • Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

  • Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
  • Invocation: Name spinngo-databingo directly; if the source includes slash commands, start with the command and then add task context.
  • Validation: Start small and check whether the result follows “📚 Tier 1 context — load when skill activates / Kontekst — hvorfor er dette kritisk? / Mapping-tabell — markedsføring vs kodenavn vs slug” before expanding.

Boundaries And Review

  • Dependencies: It usually needs no extra API key, so start with a small validation task.
  • Permissions: Declared permissions include read / write / shell-exec; ask the agent to state file, command, and rollback boundaries before acting.
  • Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.