agentleFS
mbanderasmbanderas/maestro-agora/skills/agora-start/SKILL.md

agora-start

Skill3 starsChanged 4 months agoMITView on GitHub

Help a user get started with the Maestro Agora plugin in ChatGPT or Codex, choose a first writing task, and understand which optional file and voice tools their current environment supports. Use for plugin onboarding and Agora setup questions.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check only the capabilities needed for the requested task.

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Get started with Maestro: Agora

Explain briefly that Agora drafts and edits from the user's brief, material, audience, and intended action. It needs no external account, API key, or hosted server for writing. If the user already supplied a writing task, use the bundled Agora skill to complete it. Otherwise ask for the draft or brief and its audience, then use Agora when they provide it.

In ChatGPT, users can select the installed plugin with @. In Codex, they can select $agora. /agora in a prompt is also recognized by the writing skill. Do not require a terminal command to start writing.

Optional capabilities

Check only the capabilities needed for the requested task. Ordinary writing and adapting expression from samples supplied in this conversation work without Node.js or persistent storage.

  • File audit: requires an execution tool, Node.js, and a file accessible to that execution environment. A path on the user's computer is not automatically accessible from ChatGPT on the web. If the file is unavailable, request an upload or an accessible file. If execution is unavailable, explain that the deterministic audit cannot run here. Do not present a manual inspection as a completed script audit.
  • Persistent measured voice: requires the separate Agora CLI described in the voice reference, a suitable corpus, and writable storage the user controls. Do not assume npm, network access, an installed CLI, or a persistent home directory. Check availability before using the engine; do not install it as part of onboarding. If unavailable, offer a task-only voice sketch from supplied samples without claiming a measured profile.
  • ExifTool and c2patool: optional local audit helpers. Do not install them during onboarding or report their checks as completed when absent. Use the coverage states in the publication reference.

Report only material limitations for the requested task. Do not promise that cloud files or voice profiles persist between conversations, sync across devices, or reach the Agora maintainer. User-selected files are processed in the host's execution environment, which may be cloud-hosted.

The writing skill's user-authority rules govern editorial choices within the host's instruction hierarchy. They do not override host safeguards or authorize external publication, sending messages, accessing unrelated files, or transferring data. Follow the current user's task and the host's rules.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.