/sx-configuration
Use when the user needs to generate or validate Protheus data dictionary configuration scripts -- covering SX2 (table headers), SX3 (fields), SIX (indexes), SXG (field groups), SXA (form folders/tabs), SX1 (report questions), SX5 (generic tables), SXB (F3 lookup queries), and
$ npx -y skills add thalysjuvenal/advpl-specialist --skill sx-configuration --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/sx-configuration
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when the user needs to generate or validate Protheus data dictionary configuration scripts -- covering SX2 (table headers), SX3 (fields), SIX (indexes), SXG (field groups), SXA (form folders/tabs), SX1 (report questions), SX5 (generic tables), SXB (F3 lookup queries), and
SKILL.md
sx-configuration.SKILL.mdname: sx-configuration
description: Use when the user needs to generate or validate Protheus data dictionary configuration scripts -- covering SX2 (table headers), SX3 (fields), SIX (indexes), SXG (field groups), SXA (form folders/tabs), SX1 (report questions), SX5 (generic tables), SXB (F3 lookup queries), and SX7 (triggers). Also triggers on Portuguese phrasing like "criar campo customizado", "cadastrar tabela customizada", "dicionario de dados", "criar indice SIX", "gatilho de campo", "tabela generica SX5", "consulta F3", or field-prefix names like ZA1/ZZ1.
SX Configuration
This skill provides templates and validation rules for generating Protheus data dictionary configuration scripts: SX2 table headers, SX3 field definitions, SIX indexes, SXG field groups, SXA form folders/tabs, SX1 report parameter questions, SX5 generic tables, SXB standard F3 lookup queries, and SX7 field triggers. It covers required field values, naming conventions (3-char aliases, `Z`-prefixed custom tables, `XX_FIELD` naming), share-mode semantics (`C`/`E`/`M`), and common pitfalls such as creation order (SX2 before SX3 before SIX) and hardcoded physical table names.
Activate this skill when the user is registering a new custom table, adding custom fields, defining indexes, grouping fields for cross-table validation, organizing MVC form tabs, setting up report parameter questions, creating a generic lookup table, or configuring an F3 query or field trigger. It does not cover programmatic READ access to the dictionary at runtime (`Posicione`, `TamSx3`, FW APIs) -- see `protheus-reference/sx-dictionary.md` for that.
| Reference file | Read when | |---|---| | reference.md | Always -- SX2/SX3/SIX/SXG/SXA/SX1/SX5/SXB/SX7 field templates, share modes, naming rules, and common pitfalls |
Read more
name: sx-configuration description: Use when the user needs to generate or validate Protheus data dictionary configuration scripts -- covering SX2 (table headers), SX3 (fields), SIX (indexes), SXG (field groups), SXA (form folders/tabs), SX1 (report questions), SX5 (generic tables), SXB (F3 lookup queries), and SX7 (triggers). Also triggers on Portuguese phrasing like "criar campo customizado", "cadastrar tabela customizada", "dicionario de dados", "criar indice SIX", "gatilho de campo", "tabela generica SX5", "consulta F3", or field-prefix names like ZA1/ZZ1.
SX Configuration
This skill provides templates and validation rules for generating Protheus data dictionary configuration scripts: SX2 table headers, SX3 field definitions, SIX indexes, SXG field groups, SXA form folders/tabs, SX1 report parameter questions, SX5 generic tables, SXB standard F3 lookup queries, and SX7 field triggers. It covers required field values, naming conventions (3-char aliases, `Z`-prefixed custom tables, `XX_FIELD` naming), share-mode semantics (`C`/`E`/`M`), and common pitfalls such as creation order (SX2 before SX3 before SIX) and hardcoded physical table names.
Activate this skill when the user is registering a new custom table, adding custom fields, defining indexes, grouping fields for cross-table validation, organizing MVC form tabs, setting up report parameter questions, creating a generic lookup table, or configuring an F3 query or field trigger. It does not cover programmatic READ access to the dictionary at runtime (`Posicione`, `TamSx3`, FW APIs) -- see `protheus-reference/sx-dictionary.md` for that.
| Reference file | Read when | |---|---| | reference.md | Always -- SX2/SX3/SIX/SXG/SXA/SX1/SX5/SXB/SX7 field templates, share modes, naming rules, and common pitfalls |
Plugin para Claude Code especializado em ADVPL e TLPP para desenvolvimento no ecossistema TOTVS Protheus — para desenvolvedores e consultores funcionais. Documentacao completa:
Other skills on advpl-specialist.
- /advpl-code-generation
Use 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 APIs, SOAP web services, entry points (pontos de entrada), TReport/FWMsPrinter reports, jobs, or
Open skill - /advpl-code-review
Use 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, variable scope, area management, error handling), performance bottlenecks, security vulnerabilities
Open skill - /advpl-debugging
Use when the user asks to debug, diagnose, or fix an ADVPL/TLPP error on TOTVS Protheus -- compilation errors (syntax, missing includes, undeclared variables), runtime failures (NIL access, type mismatch, array bounds), performance issues (slow queries, memory leaks), database
Open skill - /advpl-refactoring
Use when the user asks to refactor, clean up, or restructure existing ADVPL/TLPP code on TOTVS Protheus without changing its behavior -- extracting long functions (>100 lines), simplifying deeply nested conditionals, removing dead code, improving variable naming (Hungarian
Open skill - /advpl-to-tlpp-migration
Use when the user asks to migrate, convert, compatibilize, or modernize legacy ADVPL procedural code to TLPP object-oriented classes on TOTVS Protheus -- turning User Functions/Static Functions into namespaced classes with methods and data properties, replacing Private/Public
Open skill - /advpr-test-automation
Use when the user wants to write, run, or troubleshoot automated regression tests for Protheus routines with ADVPR (Advanced Protheus Robot) -- covering FWTestHelper API, TestSuite/GPS de Testes setup, headless execution via FwExecSuite, and per-pattern scripting (MVC,
Open skill

