
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Manage Konecty access profile metadata: show access definitions, inspect permissions, set field-level access, configure read/update filters, manage document-level flags. Use when the user wants to create or modify access profiles, set field permissions, add row-level filters, or control menu visibility. Requires admin credentials.
Upload, list, and delete files in Konecty document fields via the file API. Use this skill whenever the user wants to attach a file to a Konecty record, upload a photo/image to a contact or product, add a PDF or document to an opportunity, send a curriculum to a candidate, manage gallery images for a development or promotion, or attach any binary file to any Konecty module field. Also triggers when the user says 'upload', 'anexar', 'enviar arquivo', 'adicionar imagem', 'attach file', or refers to file-type fields in any document. Automatically reads field constraints (accepted extensions, max size, max file count) from metadata before uploading to catch errors early. Requires an active konecty-session (KONECTY_URL and KONECTY_TOKEN in ~/.konecty/.env or ~/.konecty/credentials).
Read Konecty metadata: list documents, get document/list/view/access/pivot/hook definitions, inspect meta types. Use when the user wants to see what metadata exists, inspect a document schema, read access profiles, view hook code, or understand metadata structure. Requires admin credentials from konecty-session.
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.
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.
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.
Opens a Konecty session via OTP login (request OTP, then verify OTP) and persists the access token in .env or ~/.konecty/credentials for use by other skills. Use when the user wants to log in to Konecty with OTP, store credentials, set up KONECTY_TOKEN, or establish a session so other Konecty skills can call the API. Only works when the namespace has OTP enabled (email or WhatsApp).
Replace with description of the skill and when the agent should use it.
Creates records in any Konecty module via POST /rest/data/:document. Guides through the full pre-creation workflow: discovering fields and types with konecty-modules, resolving lookup _ids with the built-in lookup command, checking picklist options, validating required fields, and submitting the payload. Use when the user wants to create a new record, insert data, send a message, add an activity, register a contact, create an opportunity, or create any document in Konecty. Requires an active konecty-session (KONECTY_URL and KONECTY_TOKEN in ~/.konecty/.env or ~/.konecty/credentials).
Removes a full Konecty metadata module from MetaObjects (lists, views, access, pivot, card, hooks on the document, then document/composite) via admin HTTP API with mandatory per-step confirmation. Use when retiring a document module from the tenant, cleaning NotificationPreferences-style metas, or ensuring no orphan list/view/access remain. Not for business records — use konecty-delete for /rest/data. Requires admin credentials.
Manage Konecty document metadata: show document definitions, list fields, add/remove/update fields, manage document events (queue/webhook). Use when the user wants to create or modify a document schema, add fields, manage field properties, or configure document-level events for queue/webhook integration. Requires admin credentials.
Searches and queries records in Konecty modules using the REST API. Supports simple document find (/rest/data/:document/find with GET or POST), cross-module JSON queries with relations and aggregators (/rest/query/json), and SQL queries (/rest/query/sql). Use when the user wants to search, list, filter, or query records in any Konecty module; needs to filter by field values (equals, contains, between, greater_than, in, exists, etc.); wants to join related documents and aggregate data (count, sum, avg); or needs pagination and sorting. Requires an active konecty-session (KONECTY_URL and KONECTY_TOKEN in ~/.konecty/.env). For unknown modules or field names, use konecty-modules first.
Manage Konecty list view metadata: show list definitions, manage columns, filters, sorters, calendars, and boards. Use when the user wants to create or modify list views, change column visibility or order, update default filters, or configure calendar/board views. Requires admin credentials.
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.
Manage Konecty pivot/report metadata: show pivot definitions, inspect rows/columns/values configuration, upsert pivots. Use when the user wants to create or modify pivot tables, configure row groupings, column fields, value aggregators, or default filters. Requires admin credentials.
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).
Updates records in any Konecty module via PUT /rest/data/:document. Enforces the mandatory pre-update fetch workflow: always fetch the current record first to obtain its _updatedAt (optimistic locking guard), then PUT with ids=[{_id, _updatedAt}] and data={changed fields}. Use when the user wants to update, edit, change, or modify any record in Konecty. Requires an active konecty-session. Use konecty-modules to discover field names and types before updating.
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.
Deletes a single record in any Konecty module via DELETE /rest/data/:document. Enforces a mandatory safety workflow: preview the record first, then delete one at a time with an explicit --confirm flag. Use when the user wants to delete, remove, or erase a record in Konecty. NEVER delete multiple records in a single operation. NEVER skip the preview step. Requires an active konecty-session.