acme-api

Program the Acme text editor's 9P file interface across multiple languages.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/lneely/anvillm --skill acme-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acme-api
Source: https://github.com/lneely/anvillm/tree/main/skills/acme-api
Command: npx skills add https://github.com/lneely/anvillm --skill acme-api

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the complexity of programmatically interacting with the Acme text editor, enabling seamless integration and automation of your development workflow.

Core Features & Use Cases

  • Programmatic Control: Write code to create, manipulate, and control Acme windows.
  • Event Handling: Process user interactions and editor events for dynamic tool integration.
  • Use Case: Automatically open a new Acme window, load a specific file, and pre-populate it with boilerplate code based on a template.

Quick Start

Use the acme-api skill to create a new Acme window and set its name to '/tmp/my_new_file.txt'.

Frequently Asked Questions about acme-api

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

FAQPage Schema
How do I automate window creation in the Acme text editor?

Acme automation is achieved by interacting with its 9P file interface to write control commands that programmatically create and manipulate windows. This Skill provides comprehensive guidance for programming the Acme text editor's file-based API across multiple languages.

What is the 9P protocol's role in Acme text editor automation?

Acme's 9P protocol is the file-based API that allows external programs to communicate with and control the text editor. By reading and writing files that represent Acme windows, developers can manipulate text and handle editor events programmatically.

Do I need to understand the 9P protocol to use the Acme API for automation?

Yes, using the Acme API for automation requires a solid understanding of the 9P protocol and Acme's file-based API. This prerequisite knowledge is necessary to effectively handle event processing, text manipulation, and control commands within your development workflow.

Can I handle user interaction events in Acme programmatically?

Yes, you can process user interactions and editor events for dynamic tool integration in Acme programmatically. By reading event files through the 9P interface, you can capture user actions to automate workflows and integrate external development tools directly within the editor.

What is the best way to pre-populate an Acme window with boilerplate code?

The best way to pre-populate an Acme window with boilerplate is to use the 9P interface to create a new window, set its name to a target file path, and write the template text directly into the window's body file. This enables seamless workflow automation and tool integration.