Borrowing it
Nothing to install: this file belongs to jmrplens/gitlab-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jmrplens/gitlab-mcp-server/main/.github/skills/generate-project-documentation/SKILL.mdgit clone --depth 1 https://github.com/jmrplens/gitlab-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/jmrplens/gitlab-mcp-server/generate-project-documentation)<a href="https://agentmods.dev/skills/jmrplens/gitlab-mcp-server/generate-project-documentation"><img src="https://agentmods.dev/badge/skills/jmrplens/gitlab-mcp-server/generate-project-documentation/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jmrplens/gitlab-mcp-server/generate-project-documentation"><img src="https://agentmods.dev/badge/skills/jmrplens/gitlab-mcp-server/generate-project-documentation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Agent Snooping · line 46 Skill accesses MCP server configuration files (mcp.json). MCP configs contain server URLs, authentication tokens, and tool definitions — reading them allows the skill to discover and potentially abuse other tool integrations.Fix: Remove all code or instructions that read MCP configuration files (mcp.json). MCP server details should be managed by the agent runtime, not read by individual skills.
- high Privilege Escalation · line 234 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00064 | $0.03475 |
| Opus 5.5 | $0.00026 | $0.01390 |
| Sonnet 5.5 | $0.00013 | $0.00695 |
| Haiku 4.5 | $0.00006 | $0.00347 |
Grade A, and why
generate-project-documentation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Project Documentation
Primary Directive
Generate comprehensive, well-organized documentation for the project. Analyze the entire codebase and produce a complete documentation suite covering architecture, components, APIs, developer guides, and deployment configuration.
The documentation must be:
- Accurate (absolute parity with source code)
- Organized (Diátaxis framework: Tutorials, How-to, Reference, Explanation)
- Navigable (index with cross-references between documents)
- Visual (Mermaid diagrams for architecture and data flow)
- Self-contained (no external context required to understand)
Execution Context
This skill is designed for the Documentation Writer agent or any agent tasked with producing project documentation. All output must be in English per the project language policy, with one exception the site requires: every user page also has a Spanish twin, written in the same change.
The documentation has one home per audience (ADR-0025). User documentation lives only in the Astro Starlight site, site/src/content/docs/ in English and site/src/content/docs/es/ in Spanish, published at https://docs.jmrp.io/gitlab-mcp-server/; the update-starlight-docs skill carries its page map, its generated pages and its checks. Contributor documentation lives in docs/development/. The README is a short landing page that links the site, and docs/ holds nothing beside docs/development/ but a README pointing at the site.
Analysis Phase
Before generating any documentation, complete a thorough analysis:
Step 1: Repository Structure Discovery
- Explore the complete project directory structure
- Identify all Go packages and their responsibilities
- Map the dependency graph between internal packages
- Locate existing documentation and assess gaps
- List all configuration files, build scripts, and CI/CD pipelines
Step 2: Architecture Understanding
- Read the entry point (
cmd/server/main.go) to understand initialization flow - Identify the configuration loading mechanism
- Map how the GitLab client is initialized and injected
- Understand the MCP server setup and tool registration pattern
- Trace a complete request flow from MCP client to GitLab API and back
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- today Changed 94761ae1bb78
- 6d ago Changed 81a61b0014cb
- 7d ago Changed e2825015f220
- 16d ago Changed · -4 lines · +21 tokens per session 17aec288467b
- 1mo ago Changed 8593c5fe5572
- 1mo ago Changed · +7 lines 58e9a9d64361
- 1mo ago First seen · 284 lines · 43 tokens per session scan A 589355d136f8
generate-project-documentation is a skill published in the GitHub repository jmrplens/gitlab-mcp-server (46 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 3,475 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
llm-docs-generator
Operating playbook for generating and maintaining version-pinned documentation packs with the llm-docs CLI. Use when building, refreshing, or verifying an agent-ready docs pack for a specific installed library version, or when maintaining this repository.
Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.
pptx
Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks.
doc-audit
Evaluate one project document in detail — a workbook section, big picture, strategy map, handoff message, paper, brief, or primer — without editing it. Runs the mechanical lint, builds a claim ledger, types every headline against the eight claim statuses in CLAUDE.md, traces cited evidence to the scripts and logs that…
latex-compile
Compile a LaTeX document and fix every error plus aesthetic issue (overfull/underfull boxes, widows, alignment, fonts) for a clean PDF and log. Use this instead of running pdflatex/latexmk manually — it avoids the latexmk stale-log trap and silent grep failures on binary log output, and it reformats rather than…
docx
Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4)…