Knowledge Search
dataelement/bisheng
Search the user's knowledge bases and knowledge spaces (企业知识库检索).
Vibe-sunsang knowledge base — answers questions about the level system (v2 6-axis × 7 levels), anti-patterns, workspace types, growth metrics, prompt quality, and mentoring frameworks.
Install Vibe Sunsang Knowledge
$ npx skills add fivetaku/gptaku-plugins-codex --skill vibe-sunsang-knowledge -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install fivetaku/gptaku-plugins-codex vibe-sunsang-knowledge --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-knowledge .claude/skills/vibe-sunsang-knowledge && 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-knowledge" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/vibe-sunsang-codex/skills/vibe-sunsang-knowledge into .claude/skills/vibe-sunsang-knowledge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-sunsang-knowledge", 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-knowledgeType 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-knowledge -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install fivetaku/gptaku-plugins-codex vibe-sunsang-knowledge --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-knowledge .agents/skills/vibe-sunsang-knowledge && 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-knowledge" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/vibe-sunsang-codex/skills/vibe-sunsang-knowledge into .agents/skills/vibe-sunsang-knowledge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-sunsang-knowledge", 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-knowledge -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install fivetaku/gptaku-plugins-codex vibe-sunsang-knowledge --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-knowledge .cursor/skills/vibe-sunsang-knowledge && 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-knowledge" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/vibe-sunsang-codex/skills/vibe-sunsang-knowledge into .cursor/skills/vibe-sunsang-knowledge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-sunsang-knowledge", 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-knowledge--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-knowledge -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install fivetaku/gptaku-plugins-codex vibe-sunsang-knowledge --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-knowledge .gemini/skills/vibe-sunsang-knowledge && 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-knowledge" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/vibe-sunsang-codex/skills/vibe-sunsang-knowledge into .gemini/skills/vibe-sunsang-knowledge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-sunsang-knowledge", 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-knowledgeInstalls 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-knowledge -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-knowledge .github/skills/vibe-sunsang-knowledge && 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-knowledge" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/vibe-sunsang-codex/skills/vibe-sunsang-knowledge into .github/skills/vibe-sunsang-knowledge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-sunsang-knowledge", 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-knowledge -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-knowledge --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-knowledge .opencode/skills/vibe-sunsang-knowledge && 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-knowledge" agent skill from https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/vibe-sunsang-codex/skills/vibe-sunsang-knowledge into .opencode/skills/vibe-sunsang-knowledge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-sunsang-knowledge", 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.
Facts
- Skill name
vibe-sunsang-knowledge- GitHub stars
- 128
- Token cost
- ~1.4k tokens
- SKILL.md length
- 635 words
- Files
- 16 (incl. references)
- Skills in repo
- 25
- Repo updated
- First seen
- Licence
- MIT
At a glance
Vibe-sunsang knowledge base — answers questions about the level system (v2 6-axis × 7 levels), anti-patterns, workspace types, growth metrics, prompt quality, and mentoring frameworks.
- Works in 6 steps: 워크스페이스 유형 확인 → 개념 선택 → 지식 베이스 로딩 → …
- Tasks that involve Knowledge bases
- SKILL.md covers 참조 경로, 워크스페이스 유형, 실행 흐름 and 대화 스타일, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Vibe Sunsang Knowledge is an agent skill from fivetaku/gptaku-plugins-codex. Vibe-sunsang knowledge base — answers questions about the level system (v2 6-axis × 7 levels), anti-patterns, workspace types, growth metrics, prompt quality, and mentoring frameworks. Korean triggers: "바선생 안티패턴이 뭐야?", "바선생 레벨 시스템 설명해줘", "6축이 뭐야?", "바선생 성장 지표". English triggers: "vibe-sunsang levels", "anti-patterns", "workspace types".
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 21 other files, including reference files (for example `references/builder/antipatterns.md`, `references/builder/concepts.md` and `references/builder/growth-metrics.md`).
It sits in Knowledge Management, covering Knowledge bases. The repository describes itself as: Codex-native GPTaku plugin marketplace. The licence is MIT.
When your agent uses it
- Tasks that involve Knowledge bases
Example prompts
- “vibe-sunsang levels”
- “anti-patterns”
- “workspace types”
- “/vibe-sunsang-knowledge”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit d3b47fc. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Vibe Sunsang Knowledge loads about 1.4k tokens when it runs, and up to ~52k if it reads all its reference files. Until then it costs about 90 tokens; SKILL.md has 635 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from fivetaku/gptaku-plugins-codex at commit d3b47fc, republished under its MIT licence (© fivetaku). 635 words, ~1,449 tokens.
Download SKILL.mdSave it as
.claude/skills/vibe-sunsang-knowledge/SKILL.md (or your agent's skills folder). This skill also uses 15 other files; get the full folder from GitHub.- name
- vibe-sunsang-knowledge
- description
- Vibe-sunsang knowledge base — answers questions about the level system (v2 6-axis × 7 levels), anti-patterns, workspace types, growth metrics, prompt quality, and mentoring frameworks. Korean triggers: "바선생 안티패턴이 뭐야?", "바선생 레벨 시스템 설명해줘", "6축이 뭐야?", "바선생 성장 지표". English triggers: "vibe-sunsang levels", "anti-patterns", "workspace types".
바선생 지식 베이스 (Codex)
바선생의 핵심 개념, 용어, 프레임워크에 대한 질문에 답변합니다. 설명 전용 스킬.
Codex는 skill-first다 (별도 커맨드 파일 없음). 객관식은 Codex CLI에 카드 UI가 없으므로 $PLUGIN_ROOT/shared/questioning-policy.md §A 번호 블록으로 채팅에서 묻는다.
참조 경로
- 지식 베이스:
$PLUGIN_ROOT/skills/vibe-sunsang-knowledge/references/ - 유형 설정:
~/vibe-sunsang/config/workspace_types.json
공통 (모든 워크스페이스 유형)
- 요청 품질 가이드:
$PLUGIN_ROOT/skills/vibe-sunsang-knowledge/references/common/prompt-quality.md - 멘토링 체크리스트:
$PLUGIN_ROOT/skills/vibe-sunsang-knowledge/references/common/mentoring-checklist.md - 회고 프레임워크:
$PLUGIN_ROOT/skills/vibe-sunsang-knowledge/references/common/retrospective-frameworks.md
유형별 (Builder / Explorer / Designer / Operator)
- 안티패턴:
$PLUGIN_ROOT/skills/vibe-sunsang-knowledge/references/{type}/antipatterns.md - 핵심 개념:
$PLUGIN_ROOT/skills/vibe-sunsang-knowledge/references/{type}/concepts.md - 성장 지표 & 레벨:
$PLUGIN_ROOT/skills/vibe-sunsang-knowledge/references/{type}/growth-metrics.md
워크스페이스 유형
| 유형 | 워크스페이스 목적 | 분석 기준 | 레벨 시스템 |
|---|---|---|---|
| Builder | 코딩/개발 (바이브코딩 포함) | 에러 대응, 코드 이해도, 요청 품질 | Observer → Forgemaster |
| Explorer | 리서치/Q&A/학습 | 질문 깊이, 출처 검증, 비판적 사고 | Asker → Scholar |
| Designer | 기획/아이디에이션/콘텐츠 | 기획 구체성, 구조화, 실현 가능성 | Dreamer → Visionary |
| Operator | 업무 자동화/데이터 처리 | 에러 처리, 재사용성, 문서화 | User → Automator |
실행 흐름
Step 0: 워크스페이스 유형 확인
유형별 질문인 경우 사용자의 워크스페이스 유형을 먼저 확인합니다:
~/vibe-sunsang/config/workspace_types.json을 읽어 확인- 파일이 없거나 유형 정보가 없으면
shared/questioning-policy.md §A번호 블록:
질문: 어떤 유형의 워크스페이스에 대해 알고 싶으신가요?
1. Builder (코딩) — 코딩/개발 프로젝트
2. Explorer (리서치/학습) — 리서치/Q&A/스터디
3. Designer (기획) — 기획/아이디에이션
4. Operator (자동화) — 업무 자동화/데이터처리
(모르면 가장 일반적인 1번 Builder로 설명하겠습니다)공통 주제 질문(요청 품질, 멘토링, 회고)은 유형 확인 없이 바로 진행합니다.
Step 1: 개념 선택
사용자의 질문에서 관련 주제를 파악합니다. 질문이 모호하면 두 단계 질문으로 좁혀갑니다.
먼저 shared/questioning-policy.md §A 번호 블록으로 주제 묶음을 묻습니다:
질문: 어떤 주제에 대해 알고 싶으신가요?
1. 레벨·평가 — 레벨 시스템, 6축 기술 차원, 워크스페이스 유형, 성장 지표
2. 활용·습관 — 안티패턴, 요청 품질, 멘토링 방법
(모르면 1번으로 진행하겠습니다)그 다음, 선택된 묶음에 맞는 아래 블록 하나로 개념을 묻습니다.
레벨·평가를 선택한 경우:
질문: 어떤 개념에 대해 알고 싶으신가요?
1. 레벨 시스템 — v2: 7단계(0.5 단위) 성장 레벨과 각 단계의 특징
2. 6축 기술 차원 — DECOMP/VERIFY/ORCH/FAIL/CTX/META 6가지 평가 축
3. 워크스페이스 유형 — Builder/Explorer/Designer/Operator 유형 설명
4. 성장 지표 — 유형별 성장을 측정하는 기준과 Fit Score
(여러 개면 1,3처럼 적어주세요)활용·습관을 선택한 경우:
질문: 어떤 개념에 대해 알고 싶으신가요?
1. 안티패턴 — AI 활용 시 피해야 할 나쁜 습관들
2. 요청 품질 — AI에게 좋은 요청을 하는 방법
3. 멘토링 방법 — 효과적인 AI 활용 멘토링/코칭 방법
(여러 개면 1,3처럼 적어주세요)Step 2: 지식 베이스 로딩
주제별 참조 매핑에 따라 해당 reference 파일을 읽습니다:
| 질문 유형 | 참조 파일 |
|---|---|
| 안티패턴, 나쁜 습관 | {type}/antipatterns.md |
| 레벨 시스템, 성장 단계 | {type}/growth-metrics.md |
| 6축 기술 차원, DECOMP/VERIFY 등 | {type}/growth-metrics.md + 아래 내장 설명 |
| 개념, 용어 설명 | {type}/concepts.md |
| 요청 잘 하는 법, 프롬프트 | common/prompt-quality.md |
| 멘토링, 코칭 방법 | common/mentoring-checklist.md |
| 회고, 리뷰 방법 | common/retrospective-frameworks.md |
모든 경로의 base: $PLUGIN_ROOT/skills/vibe-sunsang-knowledge/references/
Step 2-1: 6축 기술 차원 내장 설명
"6축"이나 기술 차원에 대한 질문일 경우, 다음 내용을 기반으로 설명합니다:
6대 기술 차원 (Skill Dimensions):
| 코드 | 기술 차원 | 한 줄 정의 |
|---|---|---|
| DECOMP | 작업 분해 | 복잡한 요청을 AI가 처리 가능한 단위로 나누는 능력 |
| VERIFY | 검증 전략 | AI 출력물을 비판적으로 검토하고 품질을 확인하는 능력 |
| ORCH | 오케스트레이션 | 도구, 에이전트, 워크플로우를 조합하여 활용하는 능력 |
| FAIL | 실패 대응 | 오류, 한계, 예상치 못한 결과에 대처하는 능력 |
| CTX | 맥락 관리 | AI에게 적절한 배경 정보, 제약 조건, 목표를 제공하는 능력 |
| META | 메타인지 | 자신의 AI 활용 패턴을 인식하고 전략적으로 조정하는 능력 |
유형별 가중치: 각 유형마다 중요한 축이 다릅니다.
- Builder: DECOMP(25%) + VERIFY(25%) = 50% (만드는 사람은 분해와 검증이 핵심)
- Explorer: FAIL(20%) + CTX(20%) + META(20%) = 60% (조사하는 사람은 비판적 사고가 핵심)
- Designer: CTX(25%) + META(20%) = 45% (기획하는 사람은 맥락과 전략이 핵심)
- Operator: ORCH(25%) + FAIL(20%) = 45% (운영하는 사람은 도구 조합이 핵심)
Fit Score: 6축 점수에 유형별 가중치를 곱해서 합산한 종합 점수 게이트 조건: 특정 레벨 진입 시 반드시 충족해야 하는 필수 조건 (L3 구체성>0.5, L4 검증>0.15, L5 도구>8 또는 오케스트레이션, L6 멀티에이전트, L7 외부기여) 0.5 단위: 내부는 소수점 2자리(예: 3.72), 공식 발표는 0.5 단위(예: 3.5)
Show full SKILL.md (203 more words)Show less
Step 2-2: 레벨명 테이블 (7단계, 0.5 단위)
| 레벨 | Builder | Explorer | Designer | Operator | 서사 단계 |
|---|---|---|---|---|---|
| L1 | Observer (관찰자) | Asker (질문자) | Dreamer (꿈꾸는 사람) | User (사용자) | 수동 |
| L2 | Tinkerer (만지작거리는 사람) | Curious (호기심 많은 사람) | Sketcher (스케치하는 사람) | Repeater (반복자) | 수동→능동 |
| L3 | Collaborator (협력자) | Digger (파헤치는 사람) | Shaper (다듬는 사람) | Optimizer (최적화자) | 능동 |
| L4 | Pilot (조종사) | Investigator (탐구자) | Planner (설계자) | Builder (구축자) | 능동→주도 |
| L5 | Architect (설계자) | Analyst (분석가) | Strategist (전략가) | Engineer (엔지니어) | 주도 |
| L6 | Conductor (지휘자) | Synthesizer (통합자) | Director (감독) | Orchestrator (오케스트레이터) | 주도→창조 |
| L7 | Forgemaster (대장장이) | Scholar (학자) | Visionary (비전가) | Automator (자동화 마스터) | 창조 |
레벨은 "할 수 있는가"가 아닌 **"일관되게 하는가"**를 기준으로 삼는다 (3회 일관성 원칙).
Step 3: 설명
읽은 reference 파일을 기반으로 사용자에게 설명합니다:
- 핵심 개념을 한 문장으로 요약
- 비유나 일상 예시로 쉽게 풀어 설명
- 관련된 다른 개념이 있으면 연결 (예: "6축을 이해했으니, 유형별 가중치도 궁금하시면 알려드릴게요")
대화 스타일
- 전문 용어에는 항상 쉬운 설명을 함께 제공
- 비유와 일상 예시를 적극 활용
- 한국어로 응답 (기술 용어는 영어 병기 가능)
- 한 번에 너무 많은 정보를 주지 않고, 핵심만 전달한 뒤 추가 질문을 유도
Guardrails
- 묻지 않은 전체 프레임워크를 한꺼번에 쏟아붓지 않는다.
- 예시는 AI 협업 행동에 근거를 둔다.
- 워크스페이스 유형이 불확실하면 가정을 밝힌다.
- Codex CLI에는 객관식 카드 UI가 없다 →
shared/questioning-policy.md §A번호 블록을 쓴다.
© fivetaku, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 15 other files (references) in plugins/vibe-sunsang-codex/skills/vibe-sunsang-knowledge of fivetaku/gptaku-plugins-codex.
- SKILL.md
- references/builder/antipatterns.md
- references/builder/concepts.md
- references/builder/growth-metrics.md
- references/common/mentoring-checklist.md
- references/common/prompt-quality.md
- references/common/retrospective-frameworks.md
- references/designer/antipatterns.md
- references/designer/concepts.md
- references/designer/growth-metrics.md
- references/explorer/antipatterns.md
- references/explorer/concepts.md
- references/explorer/growth-metrics.md
- references/operator/antipatterns.md
- references/operator/concepts.md
- … and 1 more
Open the folder on GitHubat commit d3b47fc
Compare with similar skills
Vibe Sunsang Knowledge 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 Knowledge this skillfivetaku/gptaku-plugins-codex | 128 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Knowledge Searchdataelement/bisheng | 12k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Capture Conversationoutline/outline | 41k | — | ~474 | Automated safety check: Pass | Custom licence | |
| Find And Citeoutline/outline | 41k | — | ~537 | Automated safety check: Pass | Custom licence | |
| Xhs Virtual Productchenjin-cmd/xhs-virtual-product | 729 | — | ~862 | Automated safety check: Pass | MIT | |
| OpenkbVectifyAI/OpenKB | 4.8k | 1 repos | ~2k | Automated safety check: Warn | Apache-2.0 |
Similar skills
Capture Conversation
outline/outline
Save the current conversation, a decision, or a set of notes as a document in an Outline collection; use when the user wants to keep what was discussed in their knowledge base.
Find And Cite
outline/outline
Answer questions from the Outline knowledge base with quotes and links to the source documents; use when the user asks what the team knows, documented, or decided about a topic.
Xhs Virtual Product
chenjin-cmd/xhs-virtual-product
This skill helps plan, select, produce, and market Xiaohongshu (RED) virtual/digital products — templates, knowledge bases, test tools, study materials.
Openkb
VectifyAI/OpenKB
A skill your agent uses when the user asks about content in their OpenKB knowledge base — research topics, concepts compiled from their documents, cross-document synthesis — or mentions openkb, an…
Learn From Materials
dmoshehun-prog/learn-from-materials
Turns books, PDFs, slides and web pages into a source-grounded knowledge base and an interactive learning page in English or Chinese, with quizzes, relationship maps and reusable methodology notes.
More from fivetaku/gptaku-plugins-codex
All 25 skills in this repoPumasi Image
fivetaku/gptaku-plugins-codex
Image-generation companion skill for the pumasi plugin family.
Insane Research Pipeline
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.
Skillers Suda
fivetaku/gptaku-plugins-codex
This skill should be used when the user asks to "스킬 만들어줘", "에이전트 만들어줘", "커맨드 만들어줘", "스킬러들의 수다", "수다", "Codex 스킬 만들어줘", "이 스킬 분석해줘", "이 스킬 개선해줘", "skill builder", "make a skill", "create a skill"…
Dd
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.
Insane Search
fivetaku/gptaku-plugins-codex
Adaptive access for blocked websites — tries every method until one works.
Docs Guide
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…"…
Related
Categories
Questions about Vibe Sunsang Knowledge
What does Vibe Sunsang Knowledge do?
Vibe-sunsang knowledge base — answers questions about the level system (v2 6-axis × 7 levels), anti-patterns, workspace types, growth metrics, prompt quality, and mentoring frameworks. Vibe Sunsang Knowledge is an agent skill from fivetaku/gptaku-plugins-codex. Vibe-sunsang knowledge base — answers questions about the level system (v2 6-axis × 7 levels), anti-patterns, workspace types, growth metrics, prompt quality, and mentoring frameworks.
When should I use Vibe Sunsang Knowledge?
Vibe Sunsang Knowledge fits situations like: tasks that involve Knowledge bases.
How do I install Vibe Sunsang Knowledge in Claude Code?
Run `npx skills add fivetaku/gptaku-plugins-codex --skill vibe-sunsang-knowledge -a claude-code`. Or copy the skill folder (plugins/vibe-sunsang-codex/skills/vibe-sunsang-knowledge in fivetaku/gptaku-plugins-codex) into .claude/skills/vibe-sunsang-knowledge in your project. Claude Code loads it when a task matches its description.
How do I install Vibe Sunsang Knowledge in Codex?
Run `npx skills add fivetaku/gptaku-plugins-codex --skill vibe-sunsang-knowledge -a codex`. Or copy the skill folder (plugins/vibe-sunsang-codex/skills/vibe-sunsang-knowledge in fivetaku/gptaku-plugins-codex) into .agents/skills/vibe-sunsang-knowledge in your project. Codex loads it when a task matches its description.
Can I use Vibe Sunsang Knowledge in Cursor, Gemini CLI or GitHub Copilot?
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-knowledge -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-knowledge, .gemini/skills/vibe-sunsang-knowledge, .github/skills/vibe-sunsang-knowledge and .opencode/skills/vibe-sunsang-knowledge in your project.
What does Vibe Sunsang Knowledge need to run?
SKILL.md names no scripts, command-line tools or credentials: Vibe Sunsang Knowledge is instructions for the agent only.
Does Vibe Sunsang Knowledge access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Vibe Sunsang Knowledge safe to install?
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.
What licence does Vibe Sunsang Knowledge use?
Vibe Sunsang Knowledge is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Vibe Sunsang Knowledge use?
About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 50k tokens, read only when the agent opens those files.
What are the alternatives to Vibe Sunsang Knowledge?
Skills that share tags, products or a category with Vibe Sunsang Knowledge: Knowledge Search (dataelement/bisheng, 12k stars), Capture Conversation (outline/outline, 41k stars), Find And Cite (outline/outline, 41k stars) and Xhs Virtual Product (chenjin-cmd/xhs-virtual-product, 729 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vibe Sunsang Knowledge?
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.