ayjnt-cli-file

Create command-line interfaces for Ayjnt agents via cli.ts files.

3|1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/northclock/ayjnt --skill ayjnt-cli-file
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ayjnt-cli-file
Source: https://github.com/northclock/ayjnt/tree/main/.claude/skills/ayjnt-cli-file
Command: npx skills add https://github.com/northclock/ayjnt --skill ayjnt-cli-file

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill bridges the gap between local development environments and agent runtimes, allowing you to trigger agent logic, workflows, and state management directly from your terminal.

Core Features & Use Cases

  • CLI Integration: Transform any Ayjnt project into a runnable program using a root-level cli.ts file.
  • Cross-Runtime Execution: Seamlessly bridge Bun-based local scripts with workerd-based agent state and Durable Objects.
  • Use Case: Build a custom CLI tool to import local file data into an agent's state, trigger background workflows, or watch agent state changes in real-time from your terminal.

Quick Start

Create a cli.ts file in your project root that exports an async function to define your command-line interface and interact with your agents.

Frequently Asked Questions about ayjnt-cli-file

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

FAQPage Schema
How do I create a command-line interface for agent apps?

You can create a command-line interface for agent apps by defining a root-level cli.ts file that exports an async function to expose agent handles and environment bindings to your host process.

Can I trigger Durable Object RPC directly from my terminal?

Yes, you can trigger Durable Object RPC directly from your terminal by bridging local Bun runtimes with workerd agent environments using a defined cli.ts file.

What is the best way to manage agent state from a local Bun runtime?

Managing agent state from a local Bun runtime involves bridging the local script with workerd-based agent environments, allowing direct interaction with agent state and workflow triggers.

Does this CLI integration approach work with workerd agent environments?

Yes, this approach works with workerd agent environments by providing a bridge that facilitates direct interaction between local Bun-based scripts and the workerd runtime.

How do I import local file data into an agent's state via a CLI?

To import local file data into an agent's state via a CLI, you build a custom CLI tool using a root-level cli.ts file to bridge your local Bun runtime with the agent environment.

Why do I need a cli.ts file to interact with agent workflows?

You need a cli.ts file because it serves as the required bridge to expose agent handles and environment bindings to the host process, enabling external shell commands to trigger agent logic.