Install
$ agentstack add skill-tbc-servicos-dataagile-agent-kit-workflow ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Consulta MCP
Antes de gerar código, consulte o MCP tbc-knowledge:
searchFluigApi({ category: "workflow" })
// → WFMovementDTO, variáveis WK*, setTaskUser, getValue/setValue, sendNotification
searchFluigPatterns({ category: "template", skill: "fluig-workflow" })
// → templates: afterStateEntry, afterProcessCreate, afterProcessFinish, funções auxiliares
searchFluigPatterns({ category: "naming" })
// → convenção wf_[nome_processo].[evento].js
Convenções e Eventos
Consulte o MCP antes de gerar o workflow:
searchFluigPatterns({ skill: "fluig-workflow", category: "naming" })
searchFluigApi({ category: "workflow" })
searchKnowledge({ skill: "fluig-dev-reference", keyword: "eventos workflow" })
Aplique naming, eventos e padrões retornados pelo MCP.
Instruções para Claude
- Perguntar antes de gerar: Qual o nome do processo? Qual o evento a ser implementado? Quais as atividades do diagrama BPM e quais regras de negócio se aplicam a cada uma?
- Consultar MCP para obter o template correto e a referência das variáveis WK* antes de implementar.
- Usar o template correto: Selecione o template correspondente ao evento solicitado. Nunca misture a assinatura de função de um evento com o corpo de outro.
- Substituir atividades genéricas: Os números de atividade nos templates são exemplos. Substitua-os pelos números reais do diagrama BPM informado pelo usuário.
- Sempre incluir log.info e log.error: Todo script deve conter
log.infono início da função principal elog.errorno blococatchcome.message. - Para setTaskUser: nunca hardcode de login: O login do usuário deve sempre vir de
getValue(), de um dataset ou de um parâmetro — nunca escrito literalmente no código.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: tbc-servicos
- Source: tbc-servicos/dataagile-agent-kit
- License: MIT
- Homepage: https://dataagile-agent-kit.dataagile.com.br
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.