协作头脑风暴
brainstorming
在实现前澄清需求、探索设计选择,并形成清晰的开发方向。
techsmith-webhooks-events【开发与工程】Process Snagit COM completion and local TechSmith artifact events with bounded watchers, stable-file checks, deduplication, and recovery. Use when a desktop workflow needs event-driven handoff without pretending TechSmith exposes webhooks. Trigger with "TechSmith events", "Snagit capture event", or "watch Camtasia output".
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
name: techsmith-webhooks-events description: >- Process Snagit COM completion and local TechSmith artifact events with bounded watchers, stable-file checks, deduplication, and recovery. Use when a desktop workflow needs event-driven handoff without pretending TechSmith exposes webhooks. Trigger with "TechSmith events", "Snagit capture event", or "watch Camtasia output". argument-hint: "[watch-directory] [event-manifest-path]" allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit version: 1.6.0 author: Jeremy Longshore jeremy@intentsolutions.io license: MIT tags:
Snagit COM offers capture event callbacks or completion polling, while local files can be observed with an operating-system watcher; these are local signals, not authenticated vendor webhooks. This skill converts noisy callbacks into durable artifact-ready events only after the file is stable and valid.
Use Read, Glob, and Grep to inspect local scripts, manifests, logs, and tests. Use WebFetch only for current primary TechSmith documentation. Use Write or Edit only after confirming the target repository file and approval boundary.
IsCaptureDone polling.TechSmith desktop activation is not API authentication. Resolve individual sign-in versus business-key or approved offline activation before execution. Redact all keys, account identifiers, activation artifacts, and sensitive endpoint details.
Do not expose the watch directory over a public endpoint, call local events webhooks, process actively written project files, or upload an artifact before authorization and validation.
Return watcher scope, event counts, deduplicated identities, stability/validation results, downstream acknowledgements, reconciled misses, dead letters, and shutdown state.
| Condition | Response |
|---|---|
| Duplicate notification | Acknowledge the existing durable identity without repeating side effects. |
| File never stabilizes | Quarantine or defer it and preserve bounded metadata. |
| Watcher overflow or restart | Run full allowlisted reconciliation from the last durable checkpoint. |
| Path not tied to an authorized job | Reject it and alert without opening the media. |
The example below shows the minimum redacted evidence expected from a successful invocation of this operator workflow.
signal=file-change; job=export-441; stable=3/3; checksum=recorded; event=artifact-ready; duplicates=2