~ / rigs / b3rys / b3rys-team-os

b3rys/b3rys-team-os

내 맥에 상주하는 AI 팀. 텔레그램·슬랙에서 일을 맡기면 누가 담당인지 정하고, 진행이 대시보드에 남습니다.

↗ GitHub ★ 17 Apache-2.0 updated 11d ago project Claude Code
share on X
ARCHETYPE
Skill Collector
Ten-plus skills loaded on demand. A procedural-knowledge library.
CONTEXT TAX · EVERY TURN
~1.7k tokens
Featherweight · median rig: 2.3k · breakdown
GUARDRAILS
0/5
No committed guardrails · details
Quality 0/100 Guardrails v2

Copy this rig

# review before running: this installs third-party code
$ npx degit b3rys/b3rys-team-os/skills ./rig-b3rys-team-os/skills
$ npx degit b3rys/b3rys-team-os/hooks ./rig-b3rys-team-os/hooks

MCP servers are added to Claude Code at local scope; env vars are shown as YOUR_… placeholders — we never store values. Files are fetched with degit into a separate folder so you can review before merging.

$ npx degit b3rys/b3rys-team-os/skills/b3os-ai-code-safety .claude/skills/b3os-ai-code-safety
$ npx degit b3rys/b3rys-team-os/skills/b3os-bwf .claude/skills/b3os-bwf
$ npx degit b3rys/b3rys-team-os/skills/b3os-github-workflow .claude/skills/b3os-github-workflow
$ npx degit b3rys/b3rys-team-os/skills/b3os-harness-playbook .claude/skills/b3os-harness-playbook
$ npx degit b3rys/b3rys-team-os/skills/b3os-how-to-explain .claude/skills/b3os-how-to-explain
$ npx degit b3rys/b3rys-team-os/skills/b3os-infra-safety .claude/skills/b3os-infra-safety
$ npx degit b3rys/b3rys-team-os/skills/b3os-mac-app-shell .claude/skills/b3os-mac-app-shell
$ npx degit b3rys/b3rys-team-os/skills/b3os-model-rollout .claude/skills/b3os-model-rollout
$ npx degit b3rys/b3rys-team-os/skills/b3os-release-ops .claude/skills/b3os-release-ops
$ npx degit b3rys/b3rys-team-os/skills/b3os-report .claude/skills/b3os-report
$ npx degit b3rys/b3rys-team-os/skills/b3os-scheduler .claude/skills/b3os-scheduler
$ npx degit b3rys/b3rys-team-os/skills/b3os-sf .claude/skills/b3os-sf
$ npx degit b3rys/b3rys-team-os/skills/b3os-slack-format .claude/skills/b3os-slack-format
$ npx degit b3rys/b3rys-team-os/skills/b3os-task-loop .claude/skills/b3os-task-loop
$ npx degit b3rys/b3rys-team-os/skills/b3os-task-mgmt .claude/skills/b3os-task-mgmt
$ npx degit b3rys/b3rys-team-os/skills/b3os-team-inbox .claude/skills/b3os-team-inbox
$ npx degit b3rys/b3rys-team-os/skills/b3os-team-learning-loop .claude/skills/b3os-team-learning-loop
$ npx degit b3rys/b3rys-team-os/skills/b3os-team-member-lifecycle .claude/skills/b3os-team-member-lifecycle
$ npx degit b3rys/b3rys-team-os/skills/b3os-telegram-file-delivery .claude/skills/b3os-telegram-file-delivery
$ npx degit b3rys/b3rys-team-os/skills/b3os-verification .claude/skills/b3os-verification
$ npx degit b3rys/b3rys-team-os/skills/b3os-workloop .claude/skills/b3os-workloop
$ npx degit b3rys/b3rys-team-os/skills/b3os .claude/skills/b3os

This rig commits no guardrails. Here is the community baseline instead — the deny/ask rules most often found across all 16.2k rigs:

{
  "permissions": {
    "deny": [
      "Read(./.env)",
      "Read(./.env.*)",
      "Read(**/.env)",
      "Read(~/.ssh/**)",
      "Bash(git push --force:*)",
      "Read(**/*.pem)",
      "Read(.env)",
      "Read(~/.aws/**)",
      "Read(**/*.key)",
      "Read(**/.env.*)",
      "Bash(git push --force*)",
      "Bash(rm -rf:*)",
      "Bash(rm -rf *)",
      "Bash(sudo *)",
      "Bash(sudo:*)",
      "Bash(rm -rf /)",
      "Bash(git push -f:*)",
      "Read(.env.*)",
      "Bash(git reset --hard*)",
      "Bash(rm -rf /*)"
    ],
    "ask": [
      "Bash(git push:*)",
      "Bash(git push *)",
      "Bash(gh pr merge *)",
      "Bash(git commit:*)",
      "Bash(rm *)",
      "Bash(gh pr merge:*)",
      "Bash(gh pr create *)",
      "Bash(git reset --hard:*)",
      "Bash(npm publish:*)",
      "Bash(git rebase *)"
    ]
  }
}

Skills (22)

Similar rigs

copied ✓