From e5b2e8b29bafab198c58071fd0b56f0e632a40e0 Mon Sep 17 00:00:00 2001 From: Aron Prins Date: Wed, 1 Apr 2026 13:56:10 +0200 Subject: [PATCH] fix(skills): address greptile review on paperclip-routines skill - Add missing `description` field to the Creating a Routine field table - Document optional `label` field available on all trigger kinds --- skills/paperclip-routines/SKILL.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/skills/paperclip-routines/SKILL.md b/skills/paperclip-routines/SKILL.md index fcad88fa..29bbc3df 100644 --- a/skills/paperclip-routines/SKILL.md +++ b/skills/paperclip-routines/SKILL.md @@ -54,6 +54,7 @@ POST /api/companies/{companyId}/routines | Field | Required | Notes | |-------|----------|-------| | `title` | yes | Max 200 chars | +| `description` | no | Human-readable description of the routine | | `assigneeAgentId` | yes | Agents: must be themselves | | `projectId` | yes | | | `goalId` | no | Inherited by run issues | @@ -92,6 +93,8 @@ Controls what happens with scheduled runs that were missed (e.g. server downtime A routine can have multiple triggers of different kinds. +All trigger kinds accept an optional `label` field (max 120 chars) — useful for distinguishing multiple triggers of the same kind on one routine. + ``` POST /api/routines/{routineId}/triggers ```