fix(skill): trim inkreach-teable description under 1024-char limit

The skill description was 1033 chars, exceeding pi's 1024-char limit and
causing a 'Skill conflicts: description exceeds 1024 characters' warning,
which prevents the skill from loading/triggering reliably.

Shortened to 990 chars while preserving all trigger-relevant keywords
(inkreach-teable/Teable, ID patterns bseXXX/tblXXX/..., configure
tables/automations, dev/deploy, systemd). Also fixed YAML folded-scalar
artifacts that injected stray spaces after slashes
('/ formSubmitted', '/ httpRequest') by avoiding line breaks after '/'.
This commit is contained in:
yeuimu
2026-08-05 09:22:26 +00:00
parent 3e06a10fe0
commit 584b75ba69
+10 -10
View File
@@ -3,16 +3,16 @@ name: inkreach-teable
description: >-
Operate a deployed inkreach-teable instance (a Teable fork with a self-built
automation engine). Configure tables, fields, records, views, and automations
(8 triggers: recordCreated/recordUpdated/recordCondition/recordCreatedOrUpdated/
formSubmitted/scheduledTime/buttonClick/webhook; 6 actions: script/sendEmail/
httpRequest/createRecord/updateRecord/getRecords), plus secrets and execution
history. Trigger when the user wants to manage tables/fields/records/views, build
or configure automations/workflows, set up button-field triggers, schedule jobs,
create webhooks, inspect run history, or troubleshoot a deployed inkreach-teable
instance — even if they don't say "inkreach-teable" but reference Teable-style IDs
(bseXXX, tblXXX, fldXXX, recXXX, viwXXX, wflXXX) or ask to configure tables and
automation on the local/deployed instance. Also covers dev/deploy tasks (build,
restart systemd services, known gotchas). Uses the inkreach-teable CLI, which targets
(8 triggers incl. recordCreated/Updated/Condition, formSubmitted, scheduledTime,
buttonClick, webhook; 6 actions: script, sendEmail, httpRequest, createRecord,
updateRecord, getRecords), plus secrets and execution history. Trigger when the
user wants to manage tables/fields/records/views, build or configure
automations/workflows, set up button-field triggers, schedule jobs, create
webhooks, inspect run history, or troubleshoot a deployed inkreach-teable
instance - even without saying "inkreach-teable" but referencing Teable-style IDs
(bseXXX, tblXXX, fldXXX, recXXX, viwXXX, wflXXX) or ask to configure
tables/automation on the local/deployed instance. Also covers dev/deploy tasks
(build, restart systemd services). Uses the inkreach-teable CLI, which targets
the project's OWN automation contract (NOT the official teable CLI).
---