Readme Generator Pro
beizhi23/README-Generator-Pro
Generate, modify, and render professional README.md files and project introduction HTML pages using the bundled README Generator Pro FastAPI application.
A skill your agent uses when the user wants to generate technical documentation for ADVPL/TLPP code on TOTVS Protheus -- Protheus.doc header blocks (@type, @param, @return, @author, @since…
Install Documentation Patterns
$ npx skills add thalysjuvenal/advpl-specialist --skill documentation-patterns -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thalysjuvenal/advpl-specialist documentation-patterns --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/thalysjuvenal/advpl-specialist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/documentation-patterns .claude/skills/documentation-patterns && 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 "documentation-patterns" agent skill from https://github.com/thalysjuvenal/advpl-specialist/tree/main/skills/documentation-patterns into .claude/skills/documentation-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-patterns", 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/thalysjuvenal/advpl-specialist/tree/main/skills/documentation-patternsType 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 thalysjuvenal/advpl-specialist --skill documentation-patterns -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thalysjuvenal/advpl-specialist documentation-patterns --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thalysjuvenal/advpl-specialist.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/documentation-patterns .agents/skills/documentation-patterns && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "documentation-patterns" agent skill from https://github.com/thalysjuvenal/advpl-specialist/tree/main/skills/documentation-patterns into .agents/skills/documentation-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-patterns", 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 thalysjuvenal/advpl-specialist --skill documentation-patterns -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thalysjuvenal/advpl-specialist documentation-patterns --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thalysjuvenal/advpl-specialist.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/documentation-patterns .cursor/skills/documentation-patterns && 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 "documentation-patterns" agent skill from https://github.com/thalysjuvenal/advpl-specialist/tree/main/skills/documentation-patterns into .cursor/skills/documentation-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-patterns", 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/thalysjuvenal/advpl-specialist.git --path skills/documentation-patterns--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 thalysjuvenal/advpl-specialist --skill documentation-patterns -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thalysjuvenal/advpl-specialist documentation-patterns --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thalysjuvenal/advpl-specialist.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/documentation-patterns .gemini/skills/documentation-patterns && 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 "documentation-patterns" agent skill from https://github.com/thalysjuvenal/advpl-specialist/tree/main/skills/documentation-patterns into .gemini/skills/documentation-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-patterns", 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 thalysjuvenal/advpl-specialist documentation-patternsInstalls 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 thalysjuvenal/advpl-specialist --skill documentation-patterns -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/thalysjuvenal/advpl-specialist.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/documentation-patterns .github/skills/documentation-patterns && 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 "documentation-patterns" agent skill from https://github.com/thalysjuvenal/advpl-specialist/tree/main/skills/documentation-patterns into .github/skills/documentation-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-patterns", 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 thalysjuvenal/advpl-specialist --skill documentation-patterns -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install thalysjuvenal/advpl-specialist documentation-patterns --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thalysjuvenal/advpl-specialist.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/documentation-patterns .opencode/skills/documentation-patterns && 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 "documentation-patterns" agent skill from https://github.com/thalysjuvenal/advpl-specialist/tree/main/skills/documentation-patterns into .opencode/skills/documentation-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-patterns", 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
documentation-patterns- GitHub stars
- 186
- Token cost
- ~514 tokens
- SKILL.md length
- 176 words
- Files
- 2
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when the user wants to generate technical documentation for ADVPL/TLPP code on TOTVS Protheus -- Protheus.doc header blocks (@type, @param, @return, @author, @since…
- The user wants to generate technical documentation for ADVPL/TLPP code on TOTVS Protheus -- Protheus.doc header blocks (@type
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Complete routine documentation (tables read/written
- REST API endpoint documentation (path/query parameters
What it does
Documentation Patterns is an agent skill from thalysjuvenal/advpl-specialist. Use when the user wants to generate technical documentation for ADVPL/TLPP code on TOTVS Protheus -- Protheus.doc header blocks (@type, @param, @return, @author, @since, @history), complete routine documentation (tables read/written, MV parameters, entry points, execution flow, dependencies), or REST API endpoint documentation (path/query parameters, request/response JSON, status codes). Also triggers on Portuguese phrasing like "documentar rotina", "gerar cabecalho Protheus.doc", "documentar endpoint"…
Its SKILL.md is about 510 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `reference.md`).
It sits in Backend & APIs, covering Technical documentation and REST APIs. The repository describes itself as: Plugin para Claude Code especializado em ADVPL e TLPP para desenvolvimento TOTVS Protheus. The licence is MIT.
When your agent uses it
- The user wants to generate technical documentation for ADVPL/TLPP code on TOTVS Protheus -- Protheus.doc header blocks (@type
- Complete routine documentation (tables read/written
- REST API endpoint documentation (path/query parameters
- Request/response JSON
Example prompts
- “documentar rotina”
- “gerar cabecalho Protheus.doc”
- “documentar endpoint”
- “/documentation-patterns”
What it can do on your machine
Read from SKILL.md and the folder at commit d80599b. 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
Documentation Patterns loads about 514 tokens when it runs. Until then it costs about 155 tokens; SKILL.md has 176 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 thalysjuvenal/advpl-specialist at commit d80599b, republished under its MIT licence (© thalysjuvenal). 176 words, ~514 tokens.
Download SKILL.mdSave it as
.claude/skills/documentation-patterns/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- documentation-patterns
- description
- Use when the user wants to generate technical documentation for ADVPL/TLPP code on TOTVS Protheus -- Protheus.doc header blocks (@type, @param, @return, @author, @since, @history), complete routine documentation (tables read/written, MV_* parameters, entry points, execution flow, dependencies), or REST API endpoint documentation (path/query parameters, request/response JSON, status codes). Also triggers on Portuguese phrasing like "documentar rotina", "gerar cabecalho Protheus.doc", "documentar endpoint", "documentar API REST", or requests to add documentation to legacy/undocumented code.
ADVPL/TLPP Documentation Patterns
This skill provides templates and a generation process for turning ADVPL/TLPP source code into Protheus-standard technical documentation. It covers three output types: a header Protheus.doc comment block for a single function/method, a full markdown routine specification (objective, module, tables read/written, MV_* parameters, entry points, execution flow, dependencies, change history), and an api REST endpoint document (authentication, path/query parameters, request body, response schemas).
Activate this skill when the user asks to generate or add documentation for existing code -- headers, full routine specs, or API docs -- following TOTVS conventions. The process reads the target file, extracts functions/parameters/tables/MV_* usage/entry points/dependencies from the code itself, cross-checks git history for author and change log when available, then fills the appropriate template.
It does not cover explaining code in plain conversational language for an audience (see code-explanation), looking up native function signatures to fill in documentation accurately (see protheus-reference), or documenting the semantics of embedded SQL macros used inside a routine (see embedded-sql).
| Reference file | Read when |
|---|---|
| reference.md | Always -- the three documentation type templates (header/full/api) and the generation process |
© thalysjuvenal, 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 1 other file in skills/documentation-patterns of thalysjuvenal/advpl-specialist.
- SKILL.md
- reference.md
Open the folder on GitHubat commit d80599b
Compare with similar skills
Documentation Patterns 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 |
|---|---|---|---|---|---|---|
| Documentation Patterns this skillthalysjuvenal/advpl-specialist | 186 | — | ~514 | Automated safety check: Pass | MIT | |
| Readme Generator Probeizhi23/README-Generator-Pro | 113 | — | ~472 | Automated safety check: Notes | None | |
| Finding TriageHacktronAI/skills | 115 | — | ~2.9k | Automated safety check: Notes | MIT | |
| OpenAPI Spec Generationwshobson/agents | 40k | 10 repos | ~511 | Automated safety check: Pass | MIT | |
| API Documentation WriterOneWave-AI/claude-skills | 323 | — | ~541 | Automated safety check: Pass | MIT | |
| API Generatinghuangjia2019/claude-code-engineering | 1.1k | 1 repos | ~426 | Automated safety check: Pass | None |
Similar skills
Finding Triage
HacktronAI/skills
Interactively validate and triage Hacktron findings against the actual source code and (optionally) a live deployment, separate true positives from false positives, adjust severity, then either…
OpenAPI Spec Generation
wshobson/agents
Create, validate and maintain OpenAPI 3.1 specs for REST APIs, whether designed first or generated from existing code, and use them for docs and client SDKs.
API Documentation Writer
OneWave-AI/claude-skills
Generate comprehensive API documentation including endpoint descriptions, request/response examples, authentication guides, error codes, and SDKs.
API Generating
huangjia2019/claude-code-engineering
Generate API endpoint documentation from Express route files.
API Documenter
alirezarezvani/claude-code-tresor
Auto-generate API documentation from code and comments. An agent skill from alirezarezvani/claude-code-tresor.
More from thalysjuvenal/advpl-specialist
All 19 skills in this repoAdvpl Code Generation
thalysjuvenal/advpl-specialist
A skill your agent uses when the user asks to generate, create, or scaffold ADVPL/TLPP code for TOTVS Protheus -- User Functions, Static Functions, TLPP classes, MVC (Model/View/Controller), REST…
Advpl Code Review
thalysjuvenal/advpl-specialist
A skill your agent uses when the user asks to review, audit, or check the quality of ADVPL/TLPP code for TOTVS Protheus before merge or deploy -- covering best practices (RecLock/MsUnlock pairing…
Advpl To Tlpp Migration
thalysjuvenal/advpl-specialist
A skill your agent uses when the user asks to migrate, convert, compatibilize, or modernize legacy ADVPL procedural code to TLPP object-oriented classes on TOTVS Protheus -- turning User…
Advpr Test Automation
thalysjuvenal/advpl-specialist
A skill your agent uses when the user wants to write, run, or troubleshoot automated regression tests for Protheus routines with ADVPR (Advanced Protheus Robot) -- covering FWTestHelper API…
Protheus Business
thalysjuvenal/advpl-specialist
A skill your agent uses when the user needs to understand a TOTVS Protheus ERP business process, module workflow, or cross-module integration -- covering Compras (COM), Estoque (EST), Faturamento…
Protheus Locks Deadlocks
thalysjuvenal/advpl-specialist
A skill your agent uses when the user needs to understand, diagnose, or prevent Protheus record locks and deadlocks -- covering RecLock/MsUnlock/SoftLock/LockByName semantics, BeginTran/EndTran…
Related
Categories
Questions about Documentation Patterns
What does Documentation Patterns do?
A skill your agent uses when the user wants to generate technical documentation for ADVPL/TLPP code on TOTVS Protheus -- Protheus.doc header blocks (@type, @param, @return, @author, @since…. Documentation Patterns is an agent skill from thalysjuvenal/advpl-specialist.doc header blocks (@type, @param, @return, @author, @since, @history), complete routine documentation (tables read/written, MV parameters, entry points, execution flow, dependencies), or REST API endpoint documentation (path/query parameters, request/response JSON, status codes).
When should I use Documentation Patterns?
Documentation Patterns fits situations like: the user wants to generate technical documentation for ADVPL/TLPP code on TOTVS Protheus -- Protheus.doc header blocks (@type; complete routine documentation (tables read/written; REST API endpoint documentation (path/query parameters; request/response JSON.
How do I install Documentation Patterns in Claude Code?
Run `npx skills add thalysjuvenal/advpl-specialist --skill documentation-patterns -a claude-code`. Or copy the skill folder (skills/documentation-patterns in thalysjuvenal/advpl-specialist) into .claude/skills/documentation-patterns in your project. Claude Code loads it when a task matches its description.
How do I install Documentation Patterns in Codex?
Run `npx skills add thalysjuvenal/advpl-specialist --skill documentation-patterns -a codex`. Or copy the skill folder (skills/documentation-patterns in thalysjuvenal/advpl-specialist) into .agents/skills/documentation-patterns in your project. Codex loads it when a task matches its description.
Can I use Documentation Patterns 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 thalysjuvenal/advpl-specialist --skill documentation-patterns -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/documentation-patterns, .gemini/skills/documentation-patterns, .github/skills/documentation-patterns and .opencode/skills/documentation-patterns in your project.
What does Documentation Patterns need to run?
SKILL.md names no scripts, command-line tools or credentials: Documentation Patterns is instructions for the agent only.
Does Documentation Patterns 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 Documentation Patterns 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 Documentation Patterns use?
Documentation Patterns 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 Documentation Patterns use?
About 514 tokens (SKILL.md is roughly 2.1k 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 Documentation Patterns?
Skills that share tags, products or a category with Documentation Patterns: Readme Generator Pro (beizhi23/README-Generator-Pro, 113 stars), Finding Triage (HacktronAI/skills, 115 stars), OpenAPI Spec Generation (wshobson/agents, 40k stars) and API Documentation Writer (OneWave-AI/claude-skills, 323 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Documentation Patterns?
thalysjuvenal (a GitHub user) maintains it in thalysjuvenal/advpl-specialist, which has 186 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on September 14, 2026.
Source: thalysjuvenal/advpl-specialist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.