New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

AdvPL/TLPP Compile in VS Code

by totvs in totvs/engpro-advpl-tlpp-skills

Compiles AdvPL and TLPP sources from VS Code with the TOTVS Developer Studio extension, handling server setup, connection and compile result reporting.

MITAuto-check passedDevelopment

Install AdvPL/TLPP Compile in VS Code

skills CLI
$ npx skills add totvs/engpro-advpl-tlpp-skills --skill advpl-tlpp-compile -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install totvs/engpro-advpl-tlpp-skills advpl-tlpp-compile --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/totvs/engpro-advpl-tlpp-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/advpl-tlpp/advpl-tlpp-compile .claude/skills/advpl-tlpp-compile && rm -rf skills-src

Use ~/.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/

Facts

Skill name
advpl-tlpp-compile
GitHub stars
143
Token cost
~3.7k tokens
SKILL.md length
1,752 words
Files
2 (incl. references)
Skills in repo
19
Repo updated
First seen
Licence
MIT

At a glance

Compiles AdvPL and TLPP sources from VS Code with the TOTVS Developer Studio extension, handling server setup, connection and compile result reporting.

  • Works in 10 steps: Confirm intent when chained after code… → Verify the extension is installed → Verify the server configuration… → …
  • Compiling a .prw or .tlpp source against a Protheus AppServer
  • SKILL.md covers Overview, When to Use, CRITICAL — Agent Execution Rules and Bundled Reference File, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Compiling in the Protheus ecosystem needs a connected, authenticated AppServer, so the skill drives the whole path. It checks that the TOTVS.tds-vscode extension is installed and installs it if missing, makes sure a server is configured in servers.json, asks which server to use when several exist, and connects. It then opens the source, runs the build or rebuild command for a file, folder or workspace, and reports the result with any compilation errors. Sources cover extensions such as .prw, .prg, .tlpp and .apw.

One rule is mandatory: the agent never asks for, reads, stores or echoes the AppServer password, and you type it into the VS Code prompt yourself. The skill is for compile requests in English or Portuguese and for code just generated or refactored. It is not for static analysis only, for other languages, or for command-line builds with tds-cli or advpls. A reference file documents the extension.

When your agent uses it

  • Compiling a .prw or .tlpp source against a Protheus AppServer
  • Recompiling after generating or refactoring AdvPL code
  • Setting up TDS for VS Code and servers.json for the first time
  • Validating that a source compiles cleanly on a server

Example prompts

  • “Compile the invoice.prw source I just changed and show any errors.”
  • “Recompile the whole workspace against the development AppServer.”
  • “Set up the TOTVS Developer Studio extension and a server entry so I can compile.”

Requirements

  • VS Code with the TOTVS.tds-vscode extension
  • A reachable Protheus AppServer registered in servers.json
  • You type the server password in the VS Code prompt yourself

Workflow steps

10 steps, taken from the step headings in SKILL.md.

  1. Confirm intent when chained after code generation
  2. Verify the extension is installed
  3. Verify the server configuration (servers.json)
  4. Configure a server through the UI (only when none exists)
  5. Select the target server
  6. Connect and authenticate
  7. Ensure CP1252 encoding
  8. Open the source file in the editor
  9. Run the compilation
  10. Report the result

What it can do on your machine

Read from SKILL.md and the folder at commit 3908e4e. 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 (its code samples are mermaid).

    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

AdvPL/TLPP Compile in VS Code loads about 3.7k tokens when it runs, and up to ~6k if it reads all its reference files. Until then it costs about 207 tokens; SKILL.md has 1,752 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~207
When it runs · the whole SKILL.md, loaded when a task matches
~3.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6k

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 totvs/engpro-advpl-tlpp-skills at commit 3908e4e, republished under its MIT licence (© totvs). 1,752 words, ~3,740 tokens.

Download SKILL.mdSave it as .claude/skills/advpl-tlpp-compile/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
advpl-tlpp-compile
description
Compile AdvPL/TLPP sources (.prw, .prg, .prx, .tlpp, .ppx, .ppp, .apw, .aph, .apl, .ahu and resources) inside VS Code using the TOTVS Developer Studio (tds-vscode) extension and the servers.json connection registry. Orchestrates the full flow: verifies the TOTVS.tds-vscode extension is installed (installs it if missing), validates/creates the server configuration in servers.json, asks the user which server to use when more than one is registered, drives the connect/authenticate step (password typed by the user — never seen by the agent), runs the build/rebuild command, and reports the compilation result. Use when user says 'compile', 'recompile', 'build source', 'compilar fonte', 'compilar prw/tlpp', 'send to RPO', 'compile in appserver', or after generating/migrating/refactoring AdvPL/TLPP code.
license
MIT
metadata.domain
Protheus
metadata.maintainer
Engenharia Protheus - Dados & DevOps
metadata.author
Kael Thornwick
metadata.version
1.0.0
metadata.category
Build and Compilation

AdvPL/TLPP Compile (tds-vscode)

Overview

Compile AdvPL and TLPP source files from inside VS Code using the TOTVS Developer Studio for VSCode extension (TOTVS.tds-vscode). Compilation in the Protheus ecosystem requires a connected and authenticated AppServer: the extension reads its connection registry from servers.json, sends the source to the server's RPO (Repository of Programs/Objects), and returns the compilation result.

This skill orchestrates the complete path so a single "compile" request works end-to-end even on a fresh machine:

  1. Ensure the extension is installed (install it if missing).
  2. Ensure a server is configured in servers.json (configure it with the user if missing).
  3. Pick the target server (ask the user when more than one exists).
  4. Connect and authenticate (the user types the password — it is never exposed to the agent).
  5. Open the target source in the editor (required before a file-scope compile).
  6. Run the build/rebuild command for the file, folder, or workspace.
  7. Report the result and surface any compilation errors.

When to Use

Use this skill when:

  • The user asks to compile or recompile an AdvPL/TLPP source (compile, recompile, build, compilar, enviar para o RPO).
  • A code-generation, migration, or refactoring skill just produced/changed .prw, .prg, .prx, .tlpp, .ppx, .ppp, .apw, .aph, .apl, or .ahu files that must be sent to the AppServer.
  • The user wants to validate that a source compiles cleanly against a server.
  • The tds-vscode extension is not yet installed or configured and the user wants to start compiling.

Do NOT use when:

  • The user only wants static analysis / linting without sending to the RPO.
  • The target language is not AdvPL/TLPP/4GL.
  • The user explicitly wants a command-line (tds-cli / advpls) build outside VS Code.

CRITICAL — Agent Execution Rules

These rules are MANDATORY.

  1. NEVER ask for, read, store, echo, or write the AppServer password. Authentication is interactive: the user types the password directly in the VS Code connection prompt. If a step needs the password, instruct the user to type it in the prompt and wait — do not collect it with any tool.
  2. ALWAYS use the extension UI to register and connect servers. Never edit servers.json by hand. Server registration goes through the Add Server assistant and connection goes through the connection prompt, so the extension validates the data and fills generated fields (id, buildVersion, secure, token) itself.
  3. NEVER write token, savedTokens, or authorizationtoken values into servers.json. Those are generated by the extension after a successful connection. The agent does not write to servers.json at all — it only reads it to detect existing servers.
  4. Ensure the source is CP1252 before compiling. The Protheus compiler only accepts Windows-1252 files. If the file was created/edited by an AI agent (UTF-8), run the utf8-to-cp1252-conversion skill first, otherwise compilation fails with garbled characters.
  5. Always confirm the target server with the user when more than one is registered. Never guess.
  6. When this skill runs as a follow-up to code generation/migration/refactoring, ASK the user whether they want to compile before starting. Do not auto-compile silently after another skill produced code.
  7. Read the result before declaring success. A command running without error is NOT proof of a successful compile — check the compilation output/Problems for errors and warnings.

Bundled Reference File

This skill uses progressive disclosure. Read the reference on demand:

Reference FileWhen to ReadContent
references/tds-vscode-reference.mdWhenever you need an exact command ID, the servers.json schema/location per OS, the list of compilable extensions, or troubleshooting guidanceFull command-ID table, servers.json schema and example, OS-specific file paths, supported extensions, common compile errors and fixes

Procedure

Follow these steps in order. Skip a step only when its precondition is already satisfied.

Step 0 — Confirm intent when chained after code generation

If this skill is being triggered automatically right after another skill produced or changed code (e.g. mvc-generator, smartx-generator, advpl-to-tlpp-migration, refactor), ask the user first whether they want to compile the generated source now. Only proceed when the user confirms. When the user invoked compilation directly, skip this step.

Step 1 — Verify the extension is installed

Check whether TOTVS.tds-vscode is installed.

  • If installed: continue to Step 2.
  • If missing: install it (extension id TOTVS.tds-vscode, name "TOTVS Developer Studio for VSCode"). After install, tell the user a window reload may be required for the TOTVS activity-bar view to appear, then continue.
Step 2 — Verify the server configuration (servers.json)

Locate servers.json (see reference for the per-OS path; default is ~/.totvsls/servers.json, or a workspace-local copy when Workspace server config is enabled).

  • File missing or configurations array empty → go to Step 3 (configure a new server).
  • One or more servers present → go to Step 4 (select a server).
Step 3 — Configure a server through the UI (only when none exists)

The extension stores connections per machine, so a configuration may legitimately not exist yet. Always register the server through the extension UI — never edit servers.json by hand.

  1. Open the Add Server assistant: trigger totvs-developer-studio.add (or click + in the TOTVS → Servers view).
  2. Ask the user to fill the assistant fields and save. Tell them exactly what each field expects:
FieldWhat to enterNotes
nameFriendly name for the servere.g. local, p12-dev
addressIP/hostname of the AppServere.g. localhost
portTCP port (the TDS/LSP port, not the SmartClient port)e.g. 2030
  1. After saving, configure the Include folders (.ch/.th definition files) via the Include assistant (totvs-developer-studio.include) — recommended for sources that use includes.

Do NOT ask for the password here. The password is requested only at connection time (Step 4). The extension fills id, buildVersion, secure, and token automatically on first connect — the agent does not write any of these.

Step 4 — Select the target server
  • Exactly one server registered → use it.
  • More than one → ask the user which server to compile against (list them by name/address:port). Never assume the default or last-connected one without confirming.
Step 5 — Connect and authenticate

Compilation requires the chosen server to be connected and authenticated with exclusive RPO access.

  • If the server is already connected, continue to Step 6.
  • Otherwise, start the connection: trigger totvs-developer-studio.connect (or totvs-developer-studio.serverSelection) for the chosen server.
  • The extension will prompt for environment, username, and password. Instruct the user to enter these in the VS Code prompt. The agent must not collect or transmit the password.
  • Wait for the connection to complete before continuing.

If compilation later fails with "It wasn't possible to obtain exclusive access to the objects repository", other users/JOBS are holding the RPO. See troubleshooting in the reference.

Show full SKILL.md (684 more words)Show less
Step 6 — Ensure CP1252 encoding

Before sending to the RPO, confirm the target source(s) are Windows-1252 encoded. If any file was generated/edited in UTF-8, run the utf8-to-cp1252-conversion skill first. Skip only if the files are already CP1252.

Step 7 — Open the source file in the editor

CRITICAL — always open the file before compiling it. The file-scope commands totvs-developer-studio.rebuild.file / build.file have no file-path argument; they act on the active text editor (bound to Ctrl+F9/Ctrl+Shift+F9 with when: editorTextFocus). If the target source is not open and focused, the command compiles the wrong file or nothing.

Open and focus each target source before running any file-scope compile.

Preferred method — open via terminal (code CLI). This is the most reliable way to open and focus a file for automation; the editor command (vscode.open) frequently fails in agent contexts:

  • run in terminal: code --reuse-window "/absolute/path/to/source.tlpp"
  • --reuse-window opens the file in the current VS Code window (does not spawn a new one)
  • the file becomes the active editor, satisfying the editorTextFocus requirement of the file-scope compile commands

Fallback method — vscode.open editor command. Only if the terminal code CLI is unavailable. Note this often returns "Failed to run command" in agent contexts even with a valid URI and skipCheck:

  • command id: vscode.open
  • args: ["file:///absolute/path/to/source.tlpp"] — a file:/// URI, not a plain path
  • skipCheck: true — required, because vscode.open is not in the validated palette list; without it the tool returns "Failed to find command"

If you need to compile several individual files, open each one (they become "open editors") and use the open editors command in Step 8.

Why this matters: calling rebuild.file without opening the source means there is no matching active editor. Prefer the code --reuse-window terminal command — it reliably opens and focuses the file. The vscode.open editor command may fail in agent contexts (returns "Failed to run command" / "Failed to find command"), so treat it only as a fallback.

Exception — folder/workspace compile: when compiling a whole folder or the workspace, you do not need to open files. Skip this step and use the workspace/folder command in Step 8.

Step 8 — Run the compilation

Choose the command that matches the scope (full IDs and shortcuts in the reference):

ScopeRecompile (build everything)Compile (incremental)ShortcutNeeds file open/focused?
Current/active filetotvs-developer-studio.rebuild.filetotvs-developer-studio.build.fileCtrl+F9 / Ctrl+Shift+F9Yes — open it in Step 7 first
All open editorstotvs-developer-studio.rebuild.openEditorstotvs-developer-studio.build.openEditorsCtrl+F10 / Ctrl+Shift+F10Open the target editors in Step 7 first
Folder / workspacetotvs-developer-studio.rebuild.workspacetotvs-developer-studio.build.workspace—No
  • For a single source: open it (Step 7) → then run the file command (no args — it targets the focused editor).
  • For a folder or many files: use the workspace command — most reliable for automation, no open editor needed.
  • Use rebuild (recompile) when in doubt — it always recompiles the source in focus.
Step 9 — Report the result

After the command finishes:

  • Inspect the TDS console / Problems view for errors and warnings.
  • If multiple files were compiled, the compile result table (totvs-developer-studio.show.result.build) summarizes per-file status.
  • Report clearly: which server/environment was used, what compiled successfully, and any failures with their messages.
  • If errors are encoding-related (mojibake, invalid characters), re-run Step 6 and recompile.

Decision Flow

mermaid
flowchart TD
    A[Compile request] --> A0{Chained after code generation?}
    A0 -- Yes --> A1[Ask user: compile now?] --> A2{Confirmed?}
    A2 -- No --> AX[Stop]
    A2 -- Yes --> B
    A0 -- No --> B{tds-vscode installed?}
    B -- No --> B1[Install TOTVS.tds-vscode] --> C
    B -- Yes --> C{servers.json has a server?}
    C -- No --> C1[Register server via Add Server UI] --> D
    C -- Yes --> D{More than one server?}
    D -- Yes --> D1[Ask which server] --> E
    D -- No --> E[Use the single server]
    E --> F{Connected & authenticated?}
    F -- No --> F1[Connect via UI; user types password] --> G
    F -- Yes --> G{Source is CP1252?}
    G -- No --> G1[Run utf8-to-cp1252-conversion] --> H
    G -- Yes --> H{File or folder scope?}
    H -- File --> H1[Open file: code --reuse-window path] --> H2[Run rebuild/build.file] --> I
    H -- Folder --> H3[Run rebuild/build.workspace] --> I
    I[Read result; report errors/success]

Anti-patterns

  • Asking for the password. Never. The user types it in the VS Code prompt.
  • Editing servers.json by hand. Always register/connect through the extension UI; manual edits can corrupt the registry and skip validation.
  • Writing tokens into servers.json. Tokens are extension-generated; manual values corrupt the registry.
  • Auto-compiling after code generation without asking. When chained, always confirm with the user first.
  • Calling rebuild.file/build.file without opening the file first. They act on the active editor only — open the source with code --reuse-window "/path/to/source" in the terminal first (preferred), or use the workspace/folder command.
  • Relying on vscode.open to open the file. It often returns "Failed to run command" in agent contexts. Prefer code --reuse-window in the terminal; use vscode.open (URI + skipCheck: true) only as a fallback.
  • Compiling without a connected server. The build commands silently fail or error without an authenticated connection.
  • Declaring success without reading the result. Always verify the console/Problems output.
  • Compiling UTF-8 files. Convert to CP1252 first.
  • Guessing the server when several exist. Always confirm with the user.

© totvs, 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 (references) in skills/advpl-tlpp/advpl-tlpp-compile of totvs/engpro-advpl-tlpp-skills.

  • SKILL.md
  • references/tds-vscode-reference.md

Open the folder on GitHubat commit 3908e4e

Compare with similar skills

AdvPL/TLPP Compile in VS Code 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.

AdvPL/TLPP Compile in VS Code compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
AdvPL/TLPP Compile in VS Code this skilltotvs/engpro-advpl-tlpp-skills143—~3.7kAutomated safety check: PassMIT
Workthreadsspecstoryai/getspecstory1.3k—~1.3kAutomated safety check: NotesApache-2.0
Excalidraw Diagram Studiotech-leads-club/agent-skills7k—~3.6kAutomated safety check: PassCC-BY-4.0
Git Worktree Managermicrosoft/WindowsAppSDK4.7k—~2kAutomated safety check: PassMIT
Roo Conflict Resolutionzgsm-ai/costrict4.4k—~2.3kAutomated safety check: PassApache-2.0
Interactive Extension TestingPowerShell/vscode-powershell1.9k—~824Automated safety check: PassMIT

Similar skills

  • Workthreads

    specstoryai/getspecstory

    SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more).

    1.3k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check: notes

  • Excalidraw Diagram Studio

    tech-leads-club/agent-skills

    Generates Excalidraw diagram files from plain descriptions, choosing among flowcharts, mind maps, architecture, swimlane, class, sequence and ER diagrams.

    7k GitHub stars~3.6k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Git Worktree Manager

    microsoft/WindowsAppSDK

    Official

    Creates and manages Git worktrees with PowerShell scripts so separate issues and Copilot sessions each get an isolated branch, build and test environment.

    4.7k GitHub stars~2k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Roo Conflict Resolution

    zgsm-ai/costrict

    Provides comprehensive guidelines for resolving merge conflicts intelligently using git history and commit context.

    4.4k GitHub stars~2.3k tokensUpdated 9 days ago
    DevelopmentAuto-check passed

  • Interactive Extension Testing

    PowerShell/vscode-powershell

    Guide for setting up the multi-root PowerShell VS Code extension/PSES dev workspace.

    1.9k GitHub stars~824 tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Release

    PowerShell/vscode-powershell

    Guide for preparing a release of the PowerShell VS Code extension.

    1.9k GitHub stars~1.1k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

More from totvs/engpro-advpl-tlpp-skills

All 19 skills in this repo

  • AdvPL UTF-8 to CP1252 Converter

    totvs/engpro-advpl-tlpp-skills

    Converts AdvPL and TLPP source files from UTF-8 to Windows-1252 in place after code generation, because the Protheus compiler accepts only CP1252 files.

    143 GitHub stars~2.6k tokensUpdated 4 days ago
    Auto-check passed

  • Protheus Spec-Driven Development

    totvs/engpro-advpl-tlpp-skills

    Plans and builds Protheus AdvPL/TLPP features through Specify, Design, Tasks and Execute phases whose depth scales with the size of the change.

    143 GitHub stars~3.6k tokensUpdated 4 days ago
    Auto-check passed

  • AdvPL and TLPP Code Review

    totvs/engpro-advpl-tlpp-skills

    Reviews AdvPL and TLPP source against SonarQube rules, ProtheusDOC requirements, security, performance and Protheus conventions, and reports findings by severity.

    143 GitHub stars~2.5k tokensUpdated 4 days ago
    Auto-check passed

  • Protheus Data Dictionary Lookup

    totvs/engpro-advpl-tlpp-skills

    Queries the TOTVS Protheus ERP data dictionary for tables, fields, indexes, parameters, triggers and lookups, including impact checks during refactoring.

    143 GitHub stars~1.5k tokensUpdated 4 days ago
    Auto-check passed

  • Protheus MVC Generator

    totvs/engpro-advpl-tlpp-skills

    Generates Protheus MVC screens in ADVPL/TLPP, with ModelDef, ViewDef, MenuDef and Browse functions for single-entity and master-detail layouts.

    143 GitHub stars~2.2k tokensUpdated 4 days ago
    Auto-check passed

  • Query Builder

    totvs/engpro-advpl-tlpp-skills

    Build optimized and safe SQL queries for Protheus tables. An agent skill from totvs/engpro-advpl-tlpp-skills.

    143 GitHub stars~4.7k tokensUpdated 4 days ago
    Auto-check passed

Works with

Categories

Questions about AdvPL/TLPP Compile in VS Code

What does AdvPL/TLPP Compile in VS Code do?

Compiles AdvPL and TLPP sources from VS Code with the TOTVS Developer Studio extension, handling server setup, connection and compile result reporting. Compiling in the Protheus ecosystem needs a connected, authenticated AppServer, so the skill drives the whole path.json, asks which server to use when several exist, and connects.

When should I use AdvPL/TLPP Compile in VS Code?

AdvPL/TLPP Compile in VS Code fits situations like: compiling a .prw or .tlpp source against a Protheus AppServer; recompiling after generating or refactoring AdvPL code; setting up TDS for VS Code and servers.json for the first time; validating that a source compiles cleanly on a server.

How do I install AdvPL/TLPP Compile in VS Code in Claude Code?

Run `npx skills add totvs/engpro-advpl-tlpp-skills --skill advpl-tlpp-compile -a claude-code`. Or copy the skill folder (skills/advpl-tlpp/advpl-tlpp-compile in totvs/engpro-advpl-tlpp-skills) into .claude/skills/advpl-tlpp-compile in your project. Claude Code loads it when a task matches its description.

How do I install AdvPL/TLPP Compile in VS Code in Codex?

Run `npx skills add totvs/engpro-advpl-tlpp-skills --skill advpl-tlpp-compile -a codex`. Or copy the skill folder (skills/advpl-tlpp/advpl-tlpp-compile in totvs/engpro-advpl-tlpp-skills) into .agents/skills/advpl-tlpp-compile in your project. Codex loads it when a task matches its description.

Can I use AdvPL/TLPP Compile in VS Code 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 totvs/engpro-advpl-tlpp-skills --skill advpl-tlpp-compile -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/advpl-tlpp-compile, .gemini/skills/advpl-tlpp-compile, .github/skills/advpl-tlpp-compile and .opencode/skills/advpl-tlpp-compile in your project.

What does AdvPL/TLPP Compile in VS Code need to run?

SKILL.md names no scripts, command-line tools or credentials: AdvPL/TLPP Compile in VS Code is instructions for the agent only. Our summary lists: VS Code with the TOTVS.tds-vscode extension; A reachable Protheus AppServer registered in servers.json; You type the server password in the VS Code prompt yourself.

Does AdvPL/TLPP Compile in VS Code 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 AdvPL/TLPP Compile in VS Code 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 AdvPL/TLPP Compile in VS Code use?

AdvPL/TLPP Compile in VS Code is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does AdvPL/TLPP Compile in VS Code use?

About 3.7k tokens (SKILL.md is roughly 15k 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 2.3k tokens, read only when the agent opens those files.

What are the alternatives to AdvPL/TLPP Compile in VS Code?

Skills that share tags, products or a category with AdvPL/TLPP Compile in VS Code: Workthreads (specstoryai/getspecstory, 1.3k stars), Excalidraw Diagram Studio (tech-leads-club/agent-skills, 7k stars), Git Worktree Manager (microsoft/WindowsAppSDK, 4.7k stars) and Roo Conflict Resolution (zgsm-ai/costrict, 4.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains AdvPL/TLPP Compile in VS Code?

totvs (a GitHub organization) maintains it in totvs/engpro-advpl-tlpp-skills, which has 143 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 5, 2026.

Source: totvs/engpro-advpl-tlpp-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.