메뉴
Fetch up-to-date library and framework docs via Context7 MCP instead of training data. USE WHEN answering setup or config questions, API references, or code examples, or when the user names a framework (e.g. React, Next.js, Prisma).
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/Sheshiyer/skill-clusters --skill documentation-lookup명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
SOC 직업 분류 기준
Arcplume runs Grok through the Grok Build CLI's own OAuth-authenticated session (grok login) for image generation, with strict preflight validation, secret-safe handling, and headless CLI-driven execution -- no separate XAI_API_KEY billing. Video falls back to the billed xAI API. USE WHEN a user wants to generate an image via a locally logged-in Grok Build CLI session, e.g. 'generate an image with grok', 'use grok build', or 'use my logged-in grok session'.
Shared reference for the Selemene cluster: the two report surfaces (deterministic Rust reports vs. narrative witness-pipeline readings), the @selemene/bridge CLI contract, the output manifest format, and non-prescriptive witnessing tone. USE WHEN deciding which Selemene surface to invoke or when routing between birth/compatibility/transit reports and solo/dyadic readings.
Route Selemene Engine tasks to the right surface: deterministic reports (birth/compatibility/transit) via selemene-core and the @selemene/bridge CLI, or narrative witness readings via selemene-report. USE WHEN the user wants anything under the Selemene/Noesis umbrella but has not named the exact surface.
| name | documentation-lookup |
| description | Fetch up-to-date library and framework docs via Context7 MCP instead of training data. USE WHEN answering setup or config questions, API references, or code examples, or when the user names a framework (e.g. React, Next.js, Prisma). |
| origin | ECC |
| cluster | research-knowledge |
| version | 1.0.0 |
When the user asks about libraries, frameworks, or APIs, fetch current documentation via the Context7 MCP (tools resolve-library-id and query-docs) instead of relying on training data.
/vercel/next.js) from a library name and query.Activate when the user:
Use this skill whenever the request depends on accurate, up-to-date behavior of a library, framework, or API. Applies across harnesses that have the Context7 MCP configured (e.g. Claude Code, Cursor, Codex).
Call the resolve-library-id MCP tool with:
Next.js, Prisma, Supabase).You must obtain a Context7-compatible library ID (format /org/project or /org/project/version) before querying docs. Do not call query-docs without a valid library ID from this step.
From the resolution results, choose one result using:
/org/project/v1.2.0).Call the query-docs MCP tool with:
/vercel/next.js).Limit: do not call query-docs (or resolve-library-id) more than 3 times per question. If the answer is unclear after 3 calls, state the uncertainty and use the best information you have rather than guessing.
libraryName: "Next.js", query: "How do I set up Next.js middleware?"./vercel/next.js) by name and benchmark score.libraryId: "/vercel/next.js", query: "How do I set up Next.js middleware?".middleware.ts example from the docs if relevant.libraryName: "Prisma", query: "How do I query with relations?"./prisma/prisma).libraryId and the query.include or select) with a short code snippet from the docs.libraryName: "Supabase", query: "What are the auth methods?".