skills.rest
friday-platform
friday-platformOFFICIAL
Explore all skills by this author →
Website𝕏@HelloFridayAIGitHub

friday-cli

Interact with a local Friday daemon via atlas CLI and HTTP API.

97|5|Updated Apr 23, 2026
Search Tags:#CLI#workspace management#HTTP API#daemon#friday#session inspection#signal triggering
One-click install
npx skills add https://github.com/friday-platform/friday-studio --skill friday-cli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: friday-cli
Source: https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/friday-cli
Command: npx skills add https://github.com/friday-platform/friday-studio --skill friday-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Interacting with a running Friday daemon for operational tasks like managing workspaces, triggering agent workflows, and inspecting session outcomes often requires memorizing complex CLI flags or manually crafting raw HTTP requests. This Skill serves as a single, authoritative reference for both the atlas CLI and the daemon's HTTP API, eliminating guesswork and reducing errors when working with Friday's runtime.

Core Features & Use Cases

  • Dual Surface Coverage: Provides complete reference material for both the human-friendly atlas CLI (for common inspection, triggering, and monitoring tasks) and the raw HTTP API (for advanced operations like partial workspace config updates, SSE streaming, and MCP registry mutations not exposed via the CLI).
  • Workflow Automation Support: Includes end-to-end recipes for common automation patterns, including creating workspaces from YAML configs, firing and monitoring signals, publishing and scoping skills, registering custom Python agents, and implementing the autopilot self-modification flywheel.
  • Safety Guardrails & Troubleshooting: Outlines clear guardrails for destructive operations, common error codes and their resolutions (e.g., 409 conflicts from active sessions, 422 payload schema errors), and guidance on when to use CLI vs HTTP for different tasks.

Quick Start

Use this skill to verify your local Friday daemon is running, list all registered workspaces, trigger a test signal on a workspace of your choice, and stream the live session events to confirm the associated agent workflow executes successfully.

Frequently Asked Questions about friday-cli

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

FAQPage Schema
How do I manage Friday daemon workspaces via command line?▼

You can manage Friday daemon workspaces by using the atlas CLI to execute operational tasks like workspace lifecycle management, signal triggering, and session inspection without manually crafting HTTP requests.

What is the difference between using the atlas CLI and the raw HTTP API for workspace management?▼

The atlas CLI handles common inspection and monitoring tasks, while the raw HTTP API supports advanced operations like partial workspace config updates, SSE streaming, and MCP registry mutations not exposed via the CLI.

How do I trigger and monitor signals on a running local daemon?▼

You can trigger and monitor signals by running atlas CLI commands to fire test signals on a workspace, then streaming live session events to verify that the associated agent workflow executes successfully.

Why does my HTTP request return a 409 conflict when interacting with the daemon?▼

A 409 conflict occurs when active sessions are running. This Skill provides troubleshooting guidance for common error codes, including 422 payload schema errors, to help resolve daemon HTTP request failures.

Can I register custom Python agents and publish skills using the CLI?▼

Yes, you can register custom Python agents and publish skills using provided atlas CLI commands and end-to-end workflow recipes designed for automating agent workflows and scoping skills.

Do I need a running local Friday daemon to use these CLI commands?▼

Yes, a running local Friday daemon is required. This Skill enables direct interaction with the daemon, and you can use it to verify daemon health before executing workspace management or signal triggering tasks.

Related Skills

Explore More Software Engineering Skills→
pohlai88pohlai88

pnpm-workspace

Define pnpm-workspace.yaml and link local packages with the workspace protocol.

Community
Intermediate
statick88statick88
1

nextjs-sse

Implements Server-Sent Events in Next.js with the WebSocket-free protocol.

Community
Intermediate
IbIFACE-TechIbIFACE-Tech

tool-integration

Create and manage custom tools and external APIs for AI agents.

Official
Advanced
ajshedivyajshedivy
4

agentos-api-workflows

Manage and execute AgentOS Workflow API endpoints via HTTP requests.

Community
Intermediate