Knowledge Search
dataelement/bisheng
Search the user's knowledge bases and knowledge spaces (企业知识库检索).
Gather, improve, and curate repository documentation and wiki content.
Install Repo Documentation Gatherer
$ npx skills add JocysCom/FocusLogger --skill repo-documentation-gatherer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install JocysCom/FocusLogger repo-documentation-gatherer --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/JocysCom/FocusLogger.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.ai/skills/repo-documentation-gatherer .claude/skills/repo-documentation-gatherer && 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 "repo-documentation-gatherer" agent skill from https://github.com/JocysCom/FocusLogger/tree/main/.ai/skills/repo-documentation-gatherer into .claude/skills/repo-documentation-gatherer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repo-documentation-gatherer", 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/JocysCom/FocusLogger/tree/main/.ai/skills/repo-documentation-gathererType 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 JocysCom/FocusLogger --skill repo-documentation-gatherer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install JocysCom/FocusLogger repo-documentation-gatherer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JocysCom/FocusLogger.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.ai/skills/repo-documentation-gatherer .agents/skills/repo-documentation-gatherer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "repo-documentation-gatherer" agent skill from https://github.com/JocysCom/FocusLogger/tree/main/.ai/skills/repo-documentation-gatherer into .agents/skills/repo-documentation-gatherer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repo-documentation-gatherer", 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 JocysCom/FocusLogger --skill repo-documentation-gatherer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install JocysCom/FocusLogger repo-documentation-gatherer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JocysCom/FocusLogger.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.ai/skills/repo-documentation-gatherer .cursor/skills/repo-documentation-gatherer && 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 "repo-documentation-gatherer" agent skill from https://github.com/JocysCom/FocusLogger/tree/main/.ai/skills/repo-documentation-gatherer into .cursor/skills/repo-documentation-gatherer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repo-documentation-gatherer", 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/JocysCom/FocusLogger.git --path .ai/skills/repo-documentation-gatherer--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 JocysCom/FocusLogger --skill repo-documentation-gatherer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install JocysCom/FocusLogger repo-documentation-gatherer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JocysCom/FocusLogger.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.ai/skills/repo-documentation-gatherer .gemini/skills/repo-documentation-gatherer && 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 "repo-documentation-gatherer" agent skill from https://github.com/JocysCom/FocusLogger/tree/main/.ai/skills/repo-documentation-gatherer into .gemini/skills/repo-documentation-gatherer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repo-documentation-gatherer", 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 JocysCom/FocusLogger repo-documentation-gathererInstalls 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 JocysCom/FocusLogger --skill repo-documentation-gatherer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/JocysCom/FocusLogger.git skills-src && mkdir -p .github/skills && cp -r skills-src/.ai/skills/repo-documentation-gatherer .github/skills/repo-documentation-gatherer && 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 "repo-documentation-gatherer" agent skill from https://github.com/JocysCom/FocusLogger/tree/main/.ai/skills/repo-documentation-gatherer into .github/skills/repo-documentation-gatherer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repo-documentation-gatherer", 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 JocysCom/FocusLogger --skill repo-documentation-gatherer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install JocysCom/FocusLogger repo-documentation-gatherer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JocysCom/FocusLogger.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.ai/skills/repo-documentation-gatherer .opencode/skills/repo-documentation-gatherer && 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 "repo-documentation-gatherer" agent skill from https://github.com/JocysCom/FocusLogger/tree/main/.ai/skills/repo-documentation-gatherer into .opencode/skills/repo-documentation-gatherer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repo-documentation-gatherer", 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
repo-documentation-gatherer- GitHub stars
- 213
- Token cost
- ~1.2k tokens
- SKILL.md length
- 603 words
- Files
- 2
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Gather, improve, and curate repository documentation and wiki content.
- Works in 3 steps: Refresh snapshot: run… → Inventory the snapshot (required):… → Curate: mirror a minimal subset of the…
- Asked to update
- SKILL.md covers Goal, Default behaviour (no questions), What is repo-relevant (generic) and KB output requirements (inside…
- Runs PowerShell scripts from its folder
What it does
Repo Documentation Gatherer is an agent skill from JocysCom/FocusLogger. Gather, improve, and curate repository documentation and wiki content. Use when asked to update, analyze, or modify WIKI instructions/documentation, or when asked to pull an external wiki snapshot into the repo and curate repo-relevant knowledge into a committed, searchable knowledge base under .ai/wiki/.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files.
It sits in Knowledge Management, covering Knowledge bases. The repository describes itself as: Find out which process or program is taking the window focus. In-game controls could temporary stop responding if other program steals the focus. The licence is GPL-3.0.
When your agent uses it
- Asked to update
- Modify WIKI instructions/documentation
- Asked to pull an external wiki snapshot into the repo and curate repo-relevant knowledge into a committed
- Searchable knowledge base under .ai/wiki/
Example prompts
- “/repo-documentation-gatherer”
Requirements
- PowerShell
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Refresh snapshot: run .ai/skills/repo-documentation-gatherer/tools/PullWikiIntoTemp.ps1 to materialize the wiki under .ai/Temp/wiki/.
- Inventory the snapshot (required): generate a complete list of snapshot markdown pages and use it as the checklist.
- Curate: mirror a minimal subset of the wiki structure under .ai/wiki/ and copy repo-relevant content into matching KB markdown files.
What it can do on your machine
Read from SKILL.md and the folder at commit b32c096. 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
Ships script files (PowerShell), which the agent can run.
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
Repo Documentation Gatherer loads about 1.2k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 603 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 JocysCom/FocusLogger at commit b32c096, republished under its GPL-3.0 licence (© JocysCom). 603 words, ~1,235 tokens.
Download SKILL.mdSave it as
.claude/skills/repo-documentation-gatherer/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- repo-documentation-gatherer
- description
- Gather, improve, and curate repository documentation and wiki content. Use when asked to update, analyze, or modify WIKI instructions/documentation, or when asked to pull an external wiki snapshot into the repo and curate repo-relevant knowledge into a committed, searchable knowledge base under `.ai/wiki/`.
Repo Documentation Gatherer (Wiki Improvement)
Goal
Keep the external wiki as the source of truth, but make its repo-relevant knowledge usable inside this code-repo workspace by maintaining:
- a raw snapshot under
.ai/Temp/wiki/(not committed) - a curated, repo-local KB under
.ai/wiki/(committed, AI-managed)
The repo-local KB must copy relevant content into .ai/wiki/ so it is indexable by repo tooling (RAG). Do not rely on links back to the external wiki for the actual guidance content.
Expectation: curate broadly across the snapshot.
Required: build an explicit review checklist of all snapshot markdown pages (.ai/Temp/wiki/**/*.md) and work through it; do not skim only a small subset.
Default behaviour (no questions)
When asked to update wiki documentation, do this without asking questions:
Refresh snapshot: run
.ai/skills/repo-documentation-gatherer/tools/PullWikiIntoTemp.ps1to materialize the wiki under.ai/Temp/wiki/.- Note: The script already knows which WIKI to pull.
Inventory the snapshot (required): generate a complete list of snapshot markdown pages and use it as the checklist.
Command (PowerShell):
powershell Get-ChildItem -Path .ai/Temp/wiki -Recurse -Filter *.md -File | Select-Object -ExpandProperty FullName- Paste this list into the PR/notes and work through it.
- Use
.orderfiles (when present) to follow intended reading order.
Curate: mirror a minimal subset of the wiki structure under
.ai/wiki/and copy repo-relevant content into matching KB markdown files.- Keep filenames and headings aligned with the snapshot where possible.
- Do not collapse everything into a single file unless the snapshot itself is tiny.
Do not ask clarifying questions about scope, target pages, or desired outcomes. Assume the task is: refresh the snapshot and curate repo-relevant content into the KB.
Only ask questions if the workflow is blocked (e.g., missing git credentials/access, missing script, or the snapshot cannot be pulled).
What is repo-relevant (generic)
Treat content as repo-relevant if it enables work in this repository.
A section is repo-relevant if it answers any of these:
- What is this repo for and who uses it?
- How to build/run/test/debug/deploy/release this repo
- Repo-specific conventions and workflows (branching/versioning, environment names, generators, directory layout)
- Required external dependencies and how to configure them locally (databases, SSO, secrets sources, URLs/ports)
- Common troubleshooting and operational runbooks
The parent wiki may contain non-coding content (process, product, domain). Curate it only when it affects working with, operating, or changing this repo.
Show full SKILL.md (242 more words)Show less
What to extract (priority order)
Extract, in order:
- Entry points (where to start, key concepts, how to navigate)
- Build/run/test primitives (prefer repo-owned scripts and commands as SSOT)
- Local environment & configuration (env names, required services, ports/URLs, where secrets come from)
- Release/deploy workflow (steps, smoke checks, rollbacks)
- Repo conventions (branching/versioning, structure, generators)
- Troubleshooting (common failures and known fixes)
Do not extract secrets, credentials, or customer-sensitive data.
KB output requirements (inside this repo)
Required entry point
The KB must contain .ai/wiki/index.md as the entry point.
Structure (required)
- Mirror a minimal subset of the snapshot structure under
.ai/wiki/(e.g.,Illuminate/,Coding-Guidelines/,Accessibility/). - Create one KB markdown per snapshot page you extract from (copy relevant sections into the matching path).
- Keep
.ai/wiki/index.mdas a short table-of-contents linking to the curated KB pages. - Remove/rename superseded KB files in the same change (no duplicates).
Content style
Write short, actionable guidance (checklists and commands). Prefer distillation, but keep the guidance content itself inside .ai/wiki/ (copy from the snapshot and distill there). Do not link back to the external wiki for long details; instead, copy any repo-relevant details that must be searchable.
Keep .ai/wiki/ in sync with the snapshot: if content is removed or materially changed in the external wiki snapshot, remove/update it in .ai/wiki/ in the same change.
Do not add any repo-derived facts, assumptions, or helpful background that is not explicitly present in the external wiki snapshot; when unsure, omit rather than invent.
© JocysCom, GPL-3.0. 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 1 other file in .ai/skills/repo-documentation-gatherer of JocysCom/FocusLogger.
- SKILL.md
- tools/PullWikiIntoTemp.ps1
Open the folder on GitHubat commit b32c096
Compare with similar skills
Repo Documentation Gatherer 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 |
|---|---|---|---|---|---|---|
| Repo Documentation Gatherer this skillJocysCom/FocusLogger | 213 | — | ~1.2k | Automated safety check: Pass | GPL-3.0 | |
| 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 JocysCom/FocusLogger
AI Self Improvement
JocysCom/FocusLogger
Update, create, improve, and synchronise this repository's AI agent instructions and related assets (including skills).
QA Tester
JocysCom/FocusLogger
Create and maintain automated tests in Microsoft-native/.NET projects with a minimal stack — MSTest runner, System.Windows.Automation for Windows desktop, Playwright for real browser smoke.
Solution Patterns
JocysCom/FocusLogger
Establish and enforce deterministic path patterns across Code ↔ UI route/menu ↔ Test for any project.
Mermaid Rasterize
JocysCom/FocusLogger
Rasterize specific mermaid blocks inside a markdown file into PNG images.
PR Review
JocysCom/FocusLogger
AI-assisted pull request review workflow for Azure DevOps Git repositories.
Repository Analysis
JocysCom/FocusLogger
Generate or refresh .ai/repository-analysis.instructions.md whenever the user needs a repository-wide map of architecture, projects, technology stack, developer workflows, CI/testing, documentation…
Related
Categories
Questions about Repo Documentation Gatherer
What does Repo Documentation Gatherer do?
Gather, improve, and curate repository documentation and wiki content. Repo Documentation Gatherer is an agent skill from JocysCom/FocusLogger. Gather, improve, and curate repository documentation and wiki content.
When should I use Repo Documentation Gatherer?
Repo Documentation Gatherer fits situations like: asked to update; modify WIKI instructions/documentation; asked to pull an external wiki snapshot into the repo and curate repo-relevant knowledge into a committed; searchable knowledge base under .ai/wiki/.
How do I install Repo Documentation Gatherer in Claude Code?
Run `npx skills add JocysCom/FocusLogger --skill repo-documentation-gatherer -a claude-code`. Or copy the skill folder (.ai/skills/repo-documentation-gatherer in JocysCom/FocusLogger) into .claude/skills/repo-documentation-gatherer in your project. Claude Code loads it when a task matches its description.
How do I install Repo Documentation Gatherer in Codex?
Run `npx skills add JocysCom/FocusLogger --skill repo-documentation-gatherer -a codex`. Or copy the skill folder (.ai/skills/repo-documentation-gatherer in JocysCom/FocusLogger) into .agents/skills/repo-documentation-gatherer in your project. Codex loads it when a task matches its description.
Can I use Repo Documentation Gatherer 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 JocysCom/FocusLogger --skill repo-documentation-gatherer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/repo-documentation-gatherer, .gemini/skills/repo-documentation-gatherer, .github/skills/repo-documentation-gatherer and .opencode/skills/repo-documentation-gatherer in your project.
What does Repo Documentation Gatherer need to run?
Going by SKILL.md and its folder, Repo Documentation Gatherer needs PowerShell for the scripts in its folder. Our summary lists: PowerShell.
Does Repo Documentation Gatherer 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 Repo Documentation Gatherer 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 Repo Documentation Gatherer use?
Repo Documentation Gatherer is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Repo Documentation Gatherer use?
About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Repo Documentation Gatherer?
Skills that share tags, products or a category with Repo Documentation Gatherer: 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 Repo Documentation Gatherer?
JocysCom (a GitHub organization) maintains it in JocysCom/FocusLogger, which has 213 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on June 30, 2026.
Source: JocysCom/FocusLogger on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.