konecty-update
No SKILL.md available for this skill.
View on GitHubMore from konecty/skills
konecty-meta-namespace
Manage Konecty Namespace global configuration: email servers, RabbitMQ queue config, storage, webhooks, plan settings, portal config. Use when the user wants to configure SMTP servers, add RabbitMQ queues, set up storage, configure global webhooks (onCreate/onUpdate/onDelete), manage Konsistent settings, or view global tenant configuration. Requires admin credentials.
9konecty-meta-view
Manage Konecty form view metadata: show view definitions, inspect visual tree (visualGroups, visualSymlinks, reverseLookups), upsert views. Use when the user wants to create or modify form layouts, rearrange fields in forms, add visual groups, or configure reverse lookups in views. Requires admin credentials.
8konecty-meta-hook
Generate and manage Konecty hook code: scriptBeforeValidation, validationData, validationScript, scriptAfterSave. Use when the user wants to create, read, update, or delete hooks, generate hook code from requirements, scaffold hook templates, or validate hook correctness. Requires admin credentials.
8konecty-meta-doctor
Validate Konecty metadata integrity: check for orphan references, missing access profiles, invalid field types, broken lookup targets, queue resource consistency, and other metadata health issues. Use when the user wants to audit metadata quality, find broken references, or validate that metadata is consistent and complete. Requires admin credentials.
8konecty-modules
Lists Konecty modules the current session has read access to, and retrieves fields and types for a specific module. Use when the user asks what modules or documents are available in Konecty, wants to know the fields/types of a module, needs to find the internal name of a module (e.g. "contatos", "clientes", "Oportunidade"), or wants to understand what data is accessible. Requires an active session from the konecty-session skill (KONECTY_URL and KONECTY_TOKEN in ~/.konecty/.env).
7konecty-meta-sync
Synchronize Konecty metadata between a filesystem repository and the database: plan changes (terraform-style diff), apply selectively, pull from production to repo. Use when the user wants to deploy metadata from a repository to production, compare repo vs database state, pull current metadata to a repository, or selectively apply metadata changes. Requires admin credentials.
6