Neat-Freak Knowledge Closeout
KKKKhazix/khazix-skills
Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.
Vibe-sunsang initial setup for Codex — self-heals the local workspace, links Codex session projects, classifies workspace types, generates AGENTS.md, and runs the first conversion.
$ npx skills add fivetaku/gptaku-plugins-codex --skill vibe-sunsang-onboard -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install fivetaku/gptaku-plugins-codex vibe-sunsang-onboard --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/fivetaku/gptaku-plugins-codex.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/vibe-sunsang-codex/skills/vibe-sunsang-onboard .claude/skills/vibe-sunsang-onboard && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "vibe-sunsang-onboard" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/vibe-sunsang-codex/skills/vibe-sunsang-onboard into .claude/skills/vibe-sunsang-onboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-sunsang-onboard", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/vibe-sunsang-codex/skills/vibe-sunsang-onboardType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add fivetaku/gptaku-plugins-codex --skill vibe-sunsang-onboard -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install fivetaku/gptaku-plugins-codex vibe-sunsang-onboard --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fivetaku/gptaku-plugins-codex.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/vibe-sunsang-codex/skills/vibe-sunsang-onboard .agents/skills/vibe-sunsang-onboard && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vibe-sunsang-onboard" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/vibe-sunsang-codex/skills/vibe-sunsang-onboard into .agents/skills/vibe-sunsang-onboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-sunsang-onboard", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add fivetaku/gptaku-plugins-codex --skill vibe-sunsang-onboard -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install fivetaku/gptaku-plugins-codex vibe-sunsang-onboard --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fivetaku/gptaku-plugins-codex.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/vibe-sunsang-codex/skills/vibe-sunsang-onboard .cursor/skills/vibe-sunsang-onboard && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vibe-sunsang-onboard" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/vibe-sunsang-codex/skills/vibe-sunsang-onboard into .cursor/skills/vibe-sunsang-onboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-sunsang-onboard", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/fivetaku/gptaku-plugins-codex.git --path plugins/vibe-sunsang-codex/skills/vibe-sunsang-onboard--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add fivetaku/gptaku-plugins-codex --skill vibe-sunsang-onboard -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install fivetaku/gptaku-plugins-codex vibe-sunsang-onboard --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fivetaku/gptaku-plugins-codex.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/vibe-sunsang-codex/skills/vibe-sunsang-onboard .gemini/skills/vibe-sunsang-onboard && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "vibe-sunsang-onboard" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/vibe-sunsang-codex/skills/vibe-sunsang-onboard into .gemini/skills/vibe-sunsang-onboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-sunsang-onboard", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install fivetaku/gptaku-plugins-codex vibe-sunsang-onboardInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add fivetaku/gptaku-plugins-codex --skill vibe-sunsang-onboard -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/fivetaku/gptaku-plugins-codex.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/vibe-sunsang-codex/skills/vibe-sunsang-onboard .github/skills/vibe-sunsang-onboard && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "vibe-sunsang-onboard" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/vibe-sunsang-codex/skills/vibe-sunsang-onboard into .github/skills/vibe-sunsang-onboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-sunsang-onboard", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add fivetaku/gptaku-plugins-codex --skill vibe-sunsang-onboard -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install fivetaku/gptaku-plugins-codex vibe-sunsang-onboard --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fivetaku/gptaku-plugins-codex.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/vibe-sunsang-codex/skills/vibe-sunsang-onboard .opencode/skills/vibe-sunsang-onboard && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vibe-sunsang-onboard" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/vibe-sunsang-codex/skills/vibe-sunsang-onboard into .opencode/skills/vibe-sunsang-onboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-sunsang-onboard", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
vibe-sunsang-onboardVibe-sunsang initial setup for Codex — self-heals the local workspace, links Codex session projects, classifies workspace types, generates AGENTS.md, and runs the first conversion.
Vibe Sunsang Onboard is an agent skill from fivetaku/gptaku-plugins-codex. Vibe-sunsang initial setup for Codex — self-heals the local workspace, links Codex session projects, classifies workspace types, generates AGENTS.md, and runs the first conversion. Korean triggers: "바선생 시작", "온보딩", "초기 설정", "초기화", "셋업". English triggers: "onboarding", "init", "setup", "start vibe-sunsang".
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Agent instruction files. It works with Git. The repository describes itself as: Codex-native GPTaku plugin marketplace. The licence is MIT.
9 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit d3b47fc. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
python3pythongitFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Vibe Sunsang Onboard loads about 2.1k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 931 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from fivetaku/gptaku-plugins-codex at commit d3b47fc, republished under its MIT licence (© fivetaku). 931 words, ~2,093 tokens.
.claude/skills/vibe-sunsang-onboard/SKILL.md (or your agent's skills folder).처음 한 번만 실행한다. 워크스페이스 자가 치유 → 프로젝트 매핑 → 유형 분류 → AGENTS.md 생성 → 첫 변환.
Codex는 skill-first다 (별도 커맨드 파일 없음). 객관식은 Codex CLI에 카드 UI가 없으므로 $PLUGIN_ROOT/shared/questioning-policy.md §A 번호 블록으로 채팅에서 묻는다 (위젯 흉내 금지).
~/vibe-sunsang/~/vibe-sunsang/config/~/vibe-sunsang/conversations/~/vibe-sunsang/exports/~/vibe-sunsang/growth-log/~/.codex/sessions/ (JSONL. $CODEX_HOME/sessions가 있으면 그쪽)$PLUGIN_ROOT/references/AGENTS-MD-TEMPLATE.md$PLUGIN_ROOT/scripts/ensure_workspace.py, $PLUGIN_ROOT/scripts/convert_sessions.py~/vibe-sunsang/ 디렉토리가 있는지 확인합니다.
이미 존재하는 경우 (재온보딩) → shared/questioning-policy.md §A 번호 블록:
질문: 이전에 설정한 바선생 데이터가 있습니다. 어떻게 할까요?
1. 새 프로젝트만 추가 — 기존 설정을 유지하면서 새 프로젝트만 추가해요 (추천)
2. 처음부터 다시 — 기존 config 파일을 백업(*.bak)하고 새로 시작해요
(모르면 1번으로 진행하겠습니다)선택에 따라:
*.bak) 후 새로 생성존재하지 않거나 v1 구조인 경우 — 디렉토리 생성/마이그레이션은 스크립트에 위임:
python3 "$PLUGIN_ROOT/scripts/ensure_workspace.py" 2>/dev/null || python "$PLUGIN_ROOT/scripts/ensure_workspace.py"이 스크립트가 config/ conversations/ exports/ growth-log/weekly/를 보장하고, v1 번호 접두사 구조(40-conversations, 90-exports, 30-growth-log, 그리고 10-scripts/*.json config)를 비파괴적으로 새 구조로 이관한다. 출력 STATUS v1_migrated면 다음과 같이 안내한다:
"이전 버전의 폴더 구조를 감지해 데이터(대화·리포트·성장로그·설정)를 새 구조로 자동 이관했습니다. 기존 파일은 덮어쓰지 않았어요."
00-system/, 20-knowledge-base/ 등 나머지 v1 잔여물은 데이터가 아니므로 그대로 두거나, 사용자가 원하면 정리하도록 안내만 한다(자동 삭제 금지).
디렉토리 생성·마이그레이션은 Step 0의
ensure_workspace.py가 이미 끝냈다. 아래는 나머지 초기화만 수행한다.
AGENTS.md 생성 (Codex가 이 폴더에서 읽는 지침 파일):
~/vibe-sunsang/AGENTS.md가 없으면:
$PLUGIN_ROOT/references/AGENTS-MD-TEMPLATE.md의 내용을 읽는다~/vibe-sunsang/AGENTS.md에 저장한다이미 있으면:
"기존 AGENTS.md를 유지합니다."
.gitignore 생성:
~/vibe-sunsang/.gitignore가 없으면 생성:
# Large conversation files
conversations/**/*.md
!conversations/INDEX.md이미 있으면 건너뛴다.
git init:
~/vibe-sunsang/.git이 없으면:
cd "$HOME/vibe-sunsang" && git init이미 있으면 건너뛴다.
$PLUGIN_ROOT/references/AGENTS-MD-TEMPLATE.md에서 읽는다.~/.codex/sessions/다. 다른 코딩 에이전트의 세션 폴더는 변환기가 읽지 않는다 (형식이 다름).다음 메시지를 사용자에게 보여줍니다:
바선생에 오신 것을 환영합니다!
바선생은 Codex와 나눈 대화를 돌아보고, AI와 더 잘 협업하는 법을 배우게 해주는 AI 멘토 에이전트입니다.
매주 한 번 여기서 이번 주 대화를 리뷰하면:
를 발견할 수 있습니다.
지금부터 초기 설정을 진행하겠습니다.
변환기로 사용 가능한 프로젝트(작업 디렉토리) 목록을 가져옵니다. Codex 세션은 각 JSONL의 session_meta.cwd로 프로젝트가 식별됩니다:
python3 "$PLUGIN_ROOT/scripts/convert_sessions.py" --list-projects --names-file "$HOME/vibe-sunsang/config/project_names.json" 2>/dev/null || python "$PLUGIN_ROOT/scripts/convert_sessions.py" --list-projects --names-file "$HOME/vibe-sunsang/config/project_names.json"출력은 cwd<TAB>sessions<TAB>display_name TSV(세션 수 내림차순)입니다.
세션 디렉토리가 없어 [ERROR]가 나오거나 목록이 비어 있으면:
"아직 Codex 대화 기록이 없습니다. 먼저 다른 프로젝트에서 Codex를 사용한 후 다시 와주세요." → 여기서 종료
프로젝트가 있으면 다음 단계로 진행합니다.
발견된 프로젝트 목록을 보여주고, 사용자에게 읽기 좋은 이름을 지정하도록 안내합니다.
안내 메시지:
Codex가 저장한 프로젝트들을 발견했습니다. 각 프로젝트에 알아보기 쉬운 이름을 붙여주세요.
경로가 복잡해 보여도 걱정하지 마세요 - 실제 작업 폴더 경로입니다.
각 프로젝트에 대해:
display_name(폴더명에서 자동 생성된 이름)을 추측값으로 쓴다. 같은 폴더명이 다른 경로에 있으면 변환기가 부모 폴더명을 접두로 붙여 구분해 준다.shared/questioning-policy.md §A 번호 블록으로 묻는다 (프로젝트별로 반복):질문: 이 프로젝트(`~/code/my-project`, 세션 12개)의 이름을 뭐라고 할까요?
1. my_project — 폴더 이름에서 추측한 이름이에요 (추천)
2. 문장으로 직접 다른 이름 알려주세요
3. 건너뛰기 — 이 프로젝트는 분석하지 않아요
(모르면 1번으로 진행하겠습니다)질문과 1번 라벨은 각 프로젝트에 맞게 동적 생성한다.
규칙:
/tmp, /private/var/folders)에서 돈 세션도 건너뜁니다.결과를 ~/vibe-sunsang/config/project_names.json에 저장합니다 (키 = cwd 경로, 값 = 표시 이름):
{
"/home/me/code/my-project": "my_project"
}각 프로젝트 폴더(cwd)의 AGENTS.md 또는 README.md를 읽어서 유형을 추론합니다.
분류 흐름:
AGENTS.md 또는 README.md를 찾아 읽기유형 분류 기준:
| 유형 | 키워드/패턴 | 설명 |
|---|---|---|
| Builder (구현자) | build, test, deploy, component, API, 코딩, 개발, 앱 | 코딩/개발 프로젝트 |
| Explorer (탐험자) | research, study, analyze, 리서치, 학습, 스터디, Q&A, 질문 | 리서치/Q&A/학습 |
| Designer (기획자) | plan, design, ideation, 기획, 아이디어, 콘텐츠, 글쓰기 | 기획/아이디에이션 |
| Operator (운영자) | automate, workflow, schedule, 자동화, 연동, 스크립트, MCP | 업무 자동화 |
AGENTS.md/README를 찾을 수 없는 경우:
.py, .js 파일이 많으면 Builder 등)각 프로젝트에 대해 shared/questioning-policy.md §A 번호 블록으로 확인한다:
질문: [프로젝트명]의 AGENTS.md를 분석해보니 [유형] 워크스페이스로 보입니다. 맞나요?
1. Builder (코딩) — 코딩/개발 프로젝트
2. Explorer (리서치/학습) — 리서치/Q&A/스터디
3. Designer (기획) — 기획/아이디에이션
4. Operator (자동화) — 업무 자동화/데이터처리
(추론한 유형이 맞으면 그 번호로, 아니면 다른 번호로 답해주세요)질문은 각 프로젝트의 이름과 추론된 유형으로 동적 생성한다.
규칙:
결과를 ~/vibe-sunsang/config/workspace_types.json에 저장:
{
"schema_version": 1,
"type_definitions": {
"builder": "코딩/개발",
"explorer": "리서치/Q&A/스터디",
"designer": "기획/아이디에이션",
"operator": "자동화/데이터처리"
},
"default_type": "builder",
"workspaces": {
"my_project": {
"type": "builder",
"name": "my_project",
"cwd": "/home/me/code/my-project",
"detected_from": "AGENTS.md",
"confirmed": true
}
}
}
workspaces의 키는 변환 결과 폴더명과 같은 표시 이름(project_names.json의 값)으로 둔다. growth/mentor 스킬이 INDEX.md의 프로젝트명으로 유형을 찾기 때문이다.
python3 "$PLUGIN_ROOT/scripts/convert_sessions.py" --force --names-file "$HOME/vibe-sunsang/config/project_names.json" --output-dir "$HOME/vibe-sunsang/conversations" 2>/dev/null || python "$PLUGIN_ROOT/scripts/convert_sessions.py" --force --names-file "$HOME/vibe-sunsang/config/project_names.json" --output-dir "$HOME/vibe-sunsang/conversations"변환 진행 상황을 보여주고, 완료되면 결과를 요약합니다:
설정 완료!
프로젝트 유형별로 맞춤 분석을 받을 수 있습니다:
| 유형 | 분석 내용 |
|---|---|
| Builder (구현자) | 코딩 요청 품질, 에러 대응, 코드 이해도 |
| Explorer (탐험자) | 질문 깊이, 출처 검증, 비판적 사고 |
| Designer (기획자) | 기획 구체성, 구조화, 실현 가능성 |
| Operator (운영자) | 자동화 품질, 에러 처리, 재사용성 |
v2 레벨 시스템:
바선생은 6가지 기술 차원으로 AI 활용 능력을 분석합니다:
| 기술 차원 | 쉬운 설명 |
|---|---|
| DECOMP (작업 분해) | 큰 요청을 작은 단계로 나누는 능력 |
| VERIFY (검증 전략) | AI 결과를 확인하고 검증하는 능력 |
| ORCH (오케스트레이션) | 여러 도구를 조합하여 활용하는 능력 |
| FAIL (실패 대응) | 오류가 나면 원인을 파악하고 대처하는 능력 |
| CTX (맥락 관리) | AI에게 필요한 정보를 잘 전달하는 능력 |
| META (메타인지) | 내가 AI를 어떻게 쓰는지 돌아보는 능력 |
레벨은 L1.0(입문)부터 L7.0(마스터)까지, 0.5 단위로 세밀하게 측정됩니다. 유형마다 중요한 축이 달라서, 나에게 맞는 맞춤 분석을 받을 수 있어요.
사용할 수 있는 기능 (Codex 스킬로 실행):
| 기능 | 설명 |
|---|---|
| "변환해줘" (vibe-sunsang-retro) | 새 대화 변환 (멘토링·성장 진입 시 자동 선행되므로 수동은 선택) |
| "멘토링해줘" (vibe-sunsang-mentor) | AI 활용 능력 코칭 (유형별 6축 맞춤, 지난 리뷰 이후 증분) |
| "성장 리포트 만들어줘" (vibe-sunsang-growth) | 성장 분석 리포트 (레벨 헤드라인 + 다음 한 수 3개) |
추천 루틴:
~/vibe-sunsang/에서 codex 실행shared/questioning-policy.md §A 번호 블록:
질문: 바로 이번 주 리뷰를 시작해볼까요?
1. 멘토링 시작 — AI 활용 능력 코칭 세션을 바로 시작해요 (6축 분석)
2. 성장 리포트 생성 — 성장 분석 리포트를 자동 생성해요 (레벨 헤드라인 + 다음 한 수)
3. 나중에 할게요 — 여기서 마무리할게요
(모르면 1번으로 진행하겠습니다)선택에 따라:
© fivetaku, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in plugins/vibe-sunsang-codex/skills/vibe-sunsang-onboard of fivetaku/gptaku-plugins-codex.
Open the folder on GitHubat commit d3b47fc
Vibe Sunsang Onboard next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Vibe Sunsang Onboard this skillfivetaku/gptaku-plugins-codex | 128 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills | 21k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Harness Evolution Feedback Looprevfactory/harness | 9.1k | — | ~855 | Automated safety check: Pass | Apache-2.0 | |
| Setup Matt Pocock Skillsywwynm/EverythingDone | 144 | 8 repos | ~1.7k | Automated safety check: Pass | GPL-3.0 | |
| Squad Agent Collaboration Patternsmicrosoft/waza | 1.4k | 4 repos | ~500 | Automated safety check: Pass | MIT | |
| Docslatitude-dev/latitude-llm | 4.7k | — | ~2.5k | Automated safety check: Pass | MIT |
KKKKhazix/khazix-skills
Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.
revfactory/harness
Collects feedback on how an agent harness performed, generalizes it, and updates the harness agents, skills and orchestrator along with a change-history table.
ywwynm/EverythingDone
Sets up an Agent skills block in AGENTS.md/CLAUDE.md and docs/agents/ so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc…
microsoft/waza
Shared collaboration rules for a team of squad agents covering worktree awareness, writing decisions to an inbox, cross-agent requests and reviewer lockout.
latitude-dev/latitude-llm
Review the current conversation context and git changes, then persist durable repository knowledge into dev-docs/.md by domain and into AGENTS.md for cross-cutting repo rules.
Apocrathia/home-assistant-config
Fix drift in Home Assistant Homelab agent context (AGENTS.md, CLAUDE.md, .agents/context/, rules, skills, agents) against the repo.
fivetaku/gptaku-plugins-codex
Image-generation companion skill for the pumasi plugin family.
fivetaku/gptaku-plugins-codex
Runs a multi-agent deep research workflow in seven phases, from scoping questions to a final report with source triangulation, state tracking and quality ratings.
fivetaku/gptaku-plugins-codex
This skill should be used when the user asks to "스킬 만들어줘", "에이전트 만들어줘", "커맨드 만들어줘", "스킬러들의 수다", "수다", "Codex 스킬 만들어줘", "이 스킬 분석해줘", "이 스킬 개선해줘", "skill builder", "make a skill", "create a skill"…
fivetaku/gptaku-plugins-codex
A skill your agent uses when the user runs /dd or /ㅇㅇ (Hangul IME alias — typing "dd" in Korean IME produces "ㅇㅇ") to act on the current OS clipboard (text or image) without pasting it into chat.
fivetaku/gptaku-plugins-codex
Adaptive access for blocked websites — tries every method until one works.
fivetaku/gptaku-plugins-codex
Fetch and explain official documentation for any library, framework, API, or service using an llms.txt-first strategy — triggers on "How do I…", "What is…", "How does X work", "Best practice for…"…
Works with
Categories
Vibe-sunsang initial setup for Codex — self-heals the local workspace, links Codex session projects, classifies workspace types, generates AGENTS.md, and runs the first conversion. Vibe Sunsang Onboard is an agent skill from fivetaku/gptaku-plugins-codex.md, and runs the first conversion.
Vibe Sunsang Onboard fits situations like: tasks that involve Agent instruction files.
Run `npx skills add fivetaku/gptaku-plugins-codex --skill vibe-sunsang-onboard -a claude-code`. Or copy the skill folder (plugins/vibe-sunsang-codex/skills/vibe-sunsang-onboard in fivetaku/gptaku-plugins-codex) into .claude/skills/vibe-sunsang-onboard in your project. Claude Code loads it when a task matches its description.
Run `npx skills add fivetaku/gptaku-plugins-codex --skill vibe-sunsang-onboard -a codex`. Or copy the skill folder (plugins/vibe-sunsang-codex/skills/vibe-sunsang-onboard in fivetaku/gptaku-plugins-codex) into .agents/skills/vibe-sunsang-onboard in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add fivetaku/gptaku-plugins-codex --skill vibe-sunsang-onboard -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vibe-sunsang-onboard, .gemini/skills/vibe-sunsang-onboard, .github/skills/vibe-sunsang-onboard and .opencode/skills/vibe-sunsang-onboard in your project.
Going by SKILL.md and its folder, Vibe Sunsang Onboard needs the command-line tools its instructions call (python3, python and git). Our summary lists: Python 3.
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Vibe Sunsang Onboard is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.1k tokens (SKILL.md is roughly 8.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Vibe Sunsang Onboard: Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars), Harness Evolution Feedback Loop (revfactory/harness, 9.1k stars), Setup Matt Pocock Skills (ywwynm/EverythingDone, 144 stars) and Squad Agent Collaboration Patterns (microsoft/waza, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
fivetaku (a GitHub user) maintains it in fivetaku/gptaku-plugins-codex, which has 128 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on September 8, 2026.
Source: fivetaku/gptaku-plugins-codex on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.