tdn-lookup
Skill183 starsChanged 2 months agoMITView on GitHub
Use as the escalation strategy when local ADVPL/TLPP reference material lacks an answer -- a tiered approach (local cache first, then TDN Confluence REST API via WebFetch, then Playwright against the API, then WebSearch, then visual site search) for looking up native functions, entry points, unknown errors, or business processes on TDN (tdn.totvs.com). Also triggers on Portuguese phrasing like "buscar documentacao no TDN", "nao encontrei na referencia local", "pesquisar funcao no TDN", "documentacao oficial TOTVS", or "erro desconhecido nao listado".
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- advpl-code-generationSkill
- advpl-code-reviewSkill
- advpl-debuggingSkill
- advpl-refactoringSkill
- advpl-to-tlpp-migrationSkill
- advpr-test-automationSkill
- changelog-patternsSkill
- code-explanationSkill
- documentation-patternsSkill
- embedded-sqlSkill
- probat-testingSkill
- protheus-businessSkill
- protheus-locks-deadlocksSkill
- protheus-referenceSkill
- query-builderSkill
- smartview-developmentSkill
- smartx-developmentSkill
- sx-configurationSkill
The file
Files
TDN Lookup — Online Search Strategy
This skill defines the standardized fallback strategy for finding official TOTVS documentation on TDN (tdn.totvs.com, a public Confluence Data Center 7.19 site with an unauthenticated REST API) whenever local reference material is insufficient. It specifies a five-tier escalation: Tier 1 always checks the relevant local cache file first (native functions, SX dictionary, common errors, entry points, business modules); Tier 2 queries the Confluence REST search API directly via WebFetch with a CQL query; Tier 3 falls back to Playwright hitting the same API when WebFetch is blocked; Tier 4 uses WebSearch plus Playwright navigation when CQL search yields nothing; Tier 5 is a last-resort manual/visual search on the TDN site itself.
Activate this skill whenever a native function, entry point, error code, or business process is not found (or only partially found) in the local reference files, or whenever the user explicitly asks for official TOTVS documentation. It does not itself contain domain knowledge -- it only orchestrates the search process; the actual native function, entry point, and error catalogs live in protheus-reference, advpl-code-generation, advpl-debugging, and protheus-business.
| Reference file | Read when |
| reference.md | Always -- tier-by-tier search strategy, CQL query construction, HTML/JSON parsing steps, fallback conditions per tier |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.