本文へ移動
cccskills
無料GitHub で公開

friendlybet-company-sports-rules

Model sports rules, event formats, prediction types, scoring implications, lock rules, data requirements, and provider constraints for FriendlyBet. Use when adding or comparing sports such as football, basketball, American football, tennis, tournaments, leagues, playoffs, brackets, weekly picks, or World Cup-specific logic.

Aviatorpo/friendlybet
インストール方法を見る

含まれるファイル（2）

  • SKILL.md3.6 KB
  • agents/openai.yaml221 B

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

FriendlyBet Sports Rules

Start Here

Read:

  • ../../company/charter.md
  • ../../company/org-map.md
  • ../../company/agents/football-rules-analyst.md
  • ../../company/agents/multi-sport-rules-analyst.md
  • ../../company/agents/data-provider-scout.md

Read playbooks only when relevant:

  • ../../company/playbooks/new-sport-expansion.md
  • ../../company/playbooks/full-company-planning-review.md
  • ../../company/playbooks/live-scoring-operations.md for World Cup group completion, final-result confidence, third-place timing, or scoring invariants.

Read academy docs when World Cup or cross-team rules knowledge matters:

  • ../../company/academy/domains/world-cup-2026-rules-and-format.md
  • ../../company/academy/domains/world-cup-rules-one-source-of-truth.md
  • ../../company/academy/domains/world-cup-official-source-register.md
  • ../../company/academy/domains/data-provider-and-live-sports-operations.md
  • ../../company/academy/handoffs/sports-rules-to-engineering-qa-content.md
  • ../../company/academy/handoffs/provider-data-to-content-engineering-qa-finops.md
  • ../../company/academy/certification/sports-rules-certification.md

Workflow

  1. Describe the real competition format before suggesting UI or schema.
  2. Separate participants, schedule, prediction types, lock rules, results, and scoring.
  3. Keep FIFA/football-specific rules out of generic sport templates unless named.
  4. Identify provider data needs and free-tier/license risks.
  5. Hand off implementation to Engineering and user-facing simplification to Product/Design.
  6. During group-completion and knockout-opening incidents, keep the rule boundary explicit: verified terminal fixtures and official advancement determine scoring/bracket readiness, with winner_code only as the resolved stored output; Story/Pundit/social readiness is not a sports-rule dependency.
  7. For tournament-aware plans, enumerate the competition phases and phase transitions that affect user state: before tournament, group stage, group completion, each knockout round active/complete, and final completion.
  8. During planning dialogue, shape any plan that touches sports formats, scoring, locks, advancement, provider data, phase transitions, or official-vs-derived results before implementation starts.
  9. Reject fast plans that skip rule boundaries, phase transitions, or official-vs-derived result semantics. Sports correctness is not optional because a shorter answer would be easier.
  10. Treat extra time and penalties as normal knockout states. The scoring-critical fact is verified advancement; penalty shootout numbers improve display/content but should not block points when advancement is safely verified.
  11. Do not treat a provider's winner field or stored winner_code as sports truth without rule validation. Sports Rules must define what makes the result safe: fixture identity, teams, stage, final/awarded state, score, result method when known, and advancing team.
  12. football-data.org is retired from final-result truth. Do not accept it as evidence for advancement, result method, winner_code, or scoreable terminal state.

Output

Return sport format model, phase/state transitions, prediction types, scoring/lock implications, provider notes, and edge cases.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

friendlybet-company-ceo

無料

Act as FriendlyBet's CEO and primary front door for every FriendlyBet request through automatic company preflight. Own end-to-end routing, planning, execution coordination, department orchestration, decision-rights enforcement, quality gates, board-style reporting, and escalation only for strategic, legal, brand, cost, risk, or taste decisions. Use by default in FriendlyBet threads, with full department planning for broad, ambiguous, strategic, cross-functional, or outcome-driven requests such as SEO, new features, multi-sport expansion, product direction, release execution, company operations, or agent coordination.

日本語の概要は準備中です。原文の説明を表示しています。

Aviatorpo/friendlybet62026年8月24日 更新

friendlybet-company-content-community

無料

Shape FriendlyBet Pundit content, bilingual product copy, community voice, share-card copy, social moments, video briefs, Hebrew/English wording, and group-chat friendly communication. Use when a task touches copy, Pundit tone, social videos, share text, community loops, or public-facing FriendlyBet voice.

日本語の概要は準備中です。原文の説明を表示しています。

Aviatorpo/friendlybet62026年8月24日 更新

friendlybet-company-design

無料

Review or design FriendlyBet user experience, visual direction, mobile-first flows, premium sports interface, Hebrew/English copy fit, RTL behavior, accessibility, interaction patterns, and product UI polish. Use when a task touches screens, flows, layout, visual hierarchy, onboarding, prediction UX, share UX, or design quality.

日本語の概要は準備中です。原文の説明を表示しています。

Aviatorpo/friendlybet62026年8月24日 更新

friendlybet-company-engineering

無料

Plan or review FriendlyBet architecture, implementation, schema, data flows, scoring, provider integrations, static/PWA behavior, Supabase/RLS impact, migrations, automation, and technical sequencing. Use when a task asks how to build, refactor, generalize, integrate, test, or safely ship FriendlyBet code.

日本語の概要は準備中です。原文の説明を表示しています。

Aviatorpo/friendlybet62026年8月24日 更新

friendlybet-company-executive

無料

Coordinate FriendlyBet company-level strategy, CEO handoff, department orchestration, HR/agent-quality escalation, operating-model decisions, multi-agent synthesis, roadmap tradeoffs, decision rights, quality gates, and updates to the virtual company system. Use when Eyal asks to involve the company, CEO, leadership, strategy, operations, several departments, or named executive agents such as Strategy Director, Chief of Staff, or Operating System Lead.

日本語の概要は準備中です。原文の説明を表示しています。

Aviatorpo/friendlybet62026年8月24日 更新

friendlybet-company-finops-enablement

無料

Control FriendlyBet operating cost, free-tier viability, provider/API cost, GitHub Actions/Supabase/Vercel usage, documentation hygiene, company memory updates, playbook maintenance, and skill validation. Use when evaluating cost, operational burden, tooling, internal docs, company memory, or whether agent profiles should become full skills.

日本語の概要は準備中です。原文の説明を表示しています。

Aviatorpo/friendlybet62026年8月24日 更新

Aviatorpo のスキルをすべて見る

このスキルの問題を報告する