konecty/konecty-meta-sync
skills/konecty-meta-sync/SKILL.md
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.
devops
Updated May 1, 2026
$ install --global
skillsauthnpx skillsauth add konecty/skills konecty-meta-syncInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 1, 2026, 9:46 AM349.9s2 files scanned
SKILL.md
- name:
- konecty-meta-sync
- description:
- 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.
Konecty Meta Sync
Synchronize metadata between a filesystem repository and the Konecty database.
Prerequisites
Requires admin credentials from konecty-session. User must have admin: true.
Requires a metadata repository with the standard structure:
MetaObjects/
Contact/
document.json
list/Default.json
view/Default.json
access/Default.json
access/Corretor.json
pivot/Default.json
hook/scriptBeforeValidation.js
hook/validationData.json
hook/validationScript.js
hook/scriptAfterSave.js
Namespace/
document.json
Workflow
1. Plan (preview changes — ALWAYS run first)
python3 scripts/meta_sync.py plan --from repo --to prod --repo /path/to/metas
python3 scripts/meta_sync.py plan --from prod --to repo --repo /path/to/metas
Shows a diff of changes that would be applied. No changes are made.
2. Apply (execute changes with confirmation)
python3 scripts/meta_sync.py apply --from repo --to prod --repo /path/to/metas
Interactive confirmation: shows each change and asks for approval.
python3 scripts/meta_sync.py apply --from repo --to prod --repo /path/to/metas --auto-approve
Non-interactive: applies all changes (for CI/CD).
python3 scripts/meta_sync.py apply --from repo --to prod --repo /path/to/metas --only Contact Contact:list:Default
Selective: applies only the specified metas.
Before each document/composite write, hooks are prevalidated using backend POST /api/admin/meta/hook/validate. Invalid hooks are skipped and reported.
3. Diff (single item comparison)
python3 scripts/meta_sync.py diff --repo /path/to/metas --meta-id Contact
python3 scripts/meta_sync.py diff --repo /path/to/metas --meta-id "Contact:list:Default"
4. Pull (fetch from prod to repo)
python3 scripts/meta_sync.py pull --repo /path/to/metas --document Contact
python3 scripts/meta_sync.py pull --repo /path/to/metas --all
Direction model
--from repo --to prod: Repository is source of truth, push to database--from prod --to repo: Database is source of truth, pull to repository
Key concepts
- Hooks (.js/.json files) in
hook/subdirectory are injected into the document meta - Hook payloads are prevalidated against backend rules before apply
- Namespace is synced as
MetaObjects/Namespace/document.json - The
--onlyflag allows selective application from a plan - The
--auto-approveflag skips interactive confirmation (for CI/CD) - After applying changes, a reload (
POST /api/admin/meta/reload) is triggered automatically
Script reference
See scripts/meta_sync.py. Stdlib only.
Related Skills
konecty/template-skill
data-ai
VerifiedTrustedCommunity
Replace with description of the skill and when the agent should use it.
SKILL.mdUpdated May 1, 2026
konecty/konecty-upload
tools
VerifiedTrustedCommunity
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).
SKILL.mdUpdated May 1, 2026
konecty/konecty-update
documentation
VerifiedTrustedCommunity
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.
SKILL.mdUpdated May 1, 2026
konecty/konecty-session
development
VerifiedTrustedCommunity
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).
SKILL.mdUpdated May 1, 2026