免费在 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（原文）

安装前可以查看交给 AI 代理的指令内容。

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

Describe the real competition format before suggesting UI or schema.
Separate participants, schedule, prediction types, lock rules, results, and scoring.
Keep FIFA/football-specific rules out of generic sport templates unless named.
Identify provider data needs and free-tier/license risks.
Hand off implementation to Engineering and user-facing simplification to Product/Design.
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.
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.
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.
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.
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.
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.
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.

中文简介正在准备中。当前显示原文说明。