본문으로 건너뛰기
cccskills
무료GitHub에 공개

friendlybet-company-privacy-security

Review FriendlyBet privacy, RLS security, auth, recovery codes, session storage, data minimization, public snapshots, share surfaces, legal/gambling wording, real-money risk, and compliance-sensitive product changes. Use when a task changes data access, user identity, public sharing, money-like language, security posture, or legal risk.

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

실행 점수 미검증

설치 방법 보기

포함된 파일(2)

  • SKILL.md2.2 KB
  • agents/openai.yaml230 B

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

FriendlyBet Privacy Security

Start Here

Read:

  • ../../company/charter.md
  • ../../company/org-map.md
  • ../../company/agents/privacy-rls-security-agent.md
  • ../../company/agents/legal-gambling-risk-reviewer.md

Read playbooks when relevant:

  • ../../company/playbooks/full-company-planning-review.md

Workflow

  1. Identify what data is collected, stored, exposed, or shared.
  2. Check RLS, anon-client access, snapshots, share pages, and recovery-code behavior.
  3. Reject unnecessary PII and server-side identity unless explicitly justified.
  4. Keep the app outside real-money gambling functionality.
  5. Suggest safer wording for public copy when needed.
  6. During planning dialogue, shape plans around RLS, PII, public snapshots, share surfaces, session/auth behavior, legal/gambling wording, and any privacy or reputation blocker before the plan is presented.
  7. Reject short-term planning shortcuts that skip data exposure, RLS, public trust, or legal/gambling wording review when those risks can affect users.
  8. For live result/scoring/public-data work, require an explicit public/private evidence boundary. Public snapshots must be allowlisted; raw provider payloads, resolver observations, workflow logs, break-glass notes, secrets, and recovery evidence stay private.
  9. Reject select=* or broad public exports in incident recovery, even when speed is tempting.

Academy

Read when public sharing, privacy training, or cross-team risk planning matters:

  • ../../company/academy/handoffs/privacy-finops-to-all.md
  • ../../company/academy/domains/privacy-security-and-public-trust.md
  • ../../company/academy/certification/privacy-finops-certification.md

Output

Return privacy/security decision, RLS/data impact, legal/gambling risk, safer wording, and blockers.

리뷰

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

댓글

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

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

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. 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의 스킬 모두 보기

이 스킬의 문제 신고