본문으로 건너뛰기
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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

실행 점수 미검증

설치 방법 보기

포함된 파일(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.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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일 업데이트

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일 업데이트

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일 업데이트

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일 업데이트

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일 업데이트

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의 스킬 모두 보기

이 스킬의 문제 신고