floatty-backend

Automate block CRUD, search, and daily-note management via the floatty-server REST API.

Updated Dec 19, 2025
One-click install
npx skills add https://github.com/float-ritual-stack/floatty --skill floatty-backend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: floatty-backend
Source: https://github.com/float-ritual-stack/floatty/tree/main/plugins/floatty-backend/skills/floatty-backend
Command: npx skills add https://github.com/float-ritual-stack/floatty --skill floatty-backend

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, jq, python3, bash, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Automates interaction with the floatty-server REST API to perform block CRUD, search, and daily-note management, enabling automation of outline data workflows without manual API composition.

Core Features & Use Cases

  • API wrappers for blocks: create, update, delete, fetch with context, and manage relationships
  • Rich search endpoints with breadcrumbs, markers, and outlinks for graph-aware queries
  • Daily-note integration via semantic endpoints to upsert pages and append to daily notes
  • Contextual tooling: block context, page topology, and export capabilities for backup and migration
  • Scripted automation: orchestrate multi-endpoint flows from scripts/ to streamline common workflows

Quick Start

Use the backend skill to automate block CRUD and daily-note management via the REST API.

Frequently Asked Questions about floatty-backend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate block CRUD operations for a REST API backend?

You can automate block CRUD operations using script-driven helpers that wrap the floatty-server REST API, enabling programmatic creation, updating, deletion, and fetching of blocks without manual API composition.

What is the best way to manage daily notes via a REST API?

Managing daily notes via a REST API uses semantic endpoints to upsert pages and append content with context and markers, enabling automated daily-note workflows directly through backend API calls.

Can I perform graph-aware searches with breadcrumbs and outlinks on backend blocks?

Yes, graph-aware searches are supported through rich search endpoints that return breadcrumbs, markers, and outlinks, allowing you to query block relationships and page topology for contextual backend data retrieval.

Do I need curl and jq to use the floatty backend automation scripts?

Yes, curl and jq are required dependencies alongside python3 and bash, as the automation scripts rely on these tools to execute REST API interactions for block and daily-note management.

How do I export blocks and page topology for backup and migration?

Export blocks and page topology for backup and migration using the contextual tooling and export capabilities exposed through the backend API, allowing programmatic retrieval and saving of structural block data.

Why use script-driven helpers instead of manual API composition for block management?

Script-driven helpers eliminate manual API composition by orchestrating multi-endpoint flows from scripts, streamlining common workflows to ensure consistent automation for block CRUD and daily-note management tasks.