blinko-api_skill

Overview

This skill provides a command-line client to manage Blinko notes and blinkos using the Blinko HTTP API. It lets you list, create, update, delete, and promote blinkos to full notes using simple Python scripts. Environment variables supply host and token so you can run it in local, CI, or server environments.

How this skill works

The scripts read BLINKO_HOST and BLINKO_TOKEN from the OS environment, defaulting BLINKO_HOST to http://127.0.0.1:1111 if unset. Commands call the Blinko API note endpoints (/v1/note/...) to perform list/get/upsert/delete operations and to promote a blinko to a note. API responses are printed to stdout; any failures write to stderr and exit with a non-zero code.

When to use it

• Quickly manage notes and short-form blinkos from a terminal or automation script.
• Automate backups or archiving of Blinko content in a CI pipeline.
• Perform bulk updates or scripted promotions of ephemeral blinkos to persistent notes.
• Integrate Blinko operations into local tooling without a web UI.

Best practices

• Set BLINKO_TOKEN and BLINKO_HOST in your environment or CI secrets, avoid hardcoding tokens in scripts.
• Test calls against a local or staging Blinko host before using production.
• Use the list and get commands to verify state before performing destructive actions like delete.
• Capture stdout responses in logs for auditing; check exit codes to detect errors in automation.

Example use cases

• List all blinkos before running a cleanup script to remove old items.
• Upsert a note from a daily automation job to capture generated summaries.
• Promote a selected blinko to a full note after editorial review via a single CLI command.
• Delete test notes created during development to keep the database clean.