nekt-agent-plugins

Guide an agency owner through getting started with Nekt — from an empty workspace to per-client context. Inspects what the workspace has so far, helps connect and organize the agency's clients' data sources (and, optionally, the agency's own internal/operational data), then hands off to build-context so agents querying the data give accurate, well-scoped answers instead of generic ones. Use this when someone is starting out, just connected the Nekt MCP and isn't sure what to do, or asks how to set up / where to begin — e.g. "começar a usar o Nekt", "onboarding da agência", "configurar meu workspace", "acabei de conectar o Nekt, e agora?", "por onde eu começo", "como organizar meus clientes no Nekt", "get started with Nekt", "set up my agency workspace", "onboard my agency", "I just connected Nekt — what now?". Inspects via list_tables / list_layers / list_volumes / get_semantic_context, guides source setup via ask_about_nekt + the Nekt web app, and hands off to build-context / edit-context.

Create and bulk-fill Nekt Context documents for an agency's clients (or a single company's business domains) so that agents querying that data give accurate, well-scoped answers instead of generic ones. Use this whenever the user wants to generate, create, organize, or set up context documents for their clients or domains, mentions clients without context, or asks to document their clients in Nekt — e.g. "gere os documentos de contexto para meus clientes", "criar contexto para todos os clientes", "organize meus clientes no Nekt", "quais clientes estão sem contexto", "set up context docs for all clients". Works through the Nekt MCP (list_tables, get_semantic_context, create_context_document, generate_sql).

Complete the missing fields in a single client's (or domain's) Nekt Context document — re-trying a data-based fill first, then asking the user for the rest, and saving the update. Use this when the user wants to finish, complete, or fill in context for a specific client/domain, or follows up after build-context — e.g. "/edit-context Padoca Digital", "completar o contexto do cliente Padoca", "preencher as informações faltantes da ACME", "finish the context doc for client X". Works through the Nekt MCP (get_semantic_context, generate_sql, execute_sql, update_context_document).

Define and manage the structure of Nekt Context documents — the field set, fill modes, naming convention, annotation grammar, and the "reference, don't duplicate" authoring rule that every per-client (or per-domain) doc follows. Use when the user wants to see, change, or standardize what a Context document should contain, or save a reusable team template — e.g. "quais campos um documento de contexto deve ter", "mudar a estrutura dos documentos de contexto", "customizar o template de contexto", "padronizar o contexto dos clientes", "salvar um template padrão pro time", "manage the context template", "what should a context doc contain", "change the context document structure". This skill owns the canonical definition that build-context and edit-context load. Reads any saved team template via get_semantic_context and persists one (opt-in) via create_context_document / update_context_document.