agentleFS
eric-wieneric-wien/ogma/skills/tickets/SKILL.md

tickets

Skill0 starsChanged 4 months agoMITView on GitHub

Pick up and work on tickets that Ogma (the Telegram bot) filed for things it couldn't do under its restrictions. Use when the user says "tickets", "what did the bot leave me", "any open tickets", "work on the ticket(s)", or "what's in the queue".

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use interview, spec and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • dazuckSkill

    interview

    Interview me about a plan to flesh out requirements before implementation. Asks non-obvious questions one at a time until all ambiguities are resolved.

    Also in 3 projects that use this

  • SentrySkill

    spec

    Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.

    Also in 4 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 5 projects that use this

  • Hugging FaceSkill

    implement

    Make tests pass. Invoke after /write-tests produces failing tests.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Read ~/ogma/tickets/ (the top level only.

    line 22
  2. Distinctive:

    Read the full ticket. Confirm with the user which one to tackle if there are several.

    line 26
  3. Distinctive:

    Do the work in this session (you have full tools here).

    line 27
  4. Distinctive:

    When finished, resolve it:

    line 28
  5. Distinctive:

    Don't auto-resolve a ticket you only partially addressed — leave it open and note progress.

    line 36
  6. Very specific:

    If a ticket is unclear, leave it open and ask the user (or message back via ~/ogma/bin/tg-send) for detail.

    line 37

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “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

Tickets

Ogma runs on Telegram with a deliberately limited toolset (read-only + web + the ogmactl whitelist). When it hits something it can't do — editing files, writing code, running arbitrary commands — it files a ticket via ogmactl ticket "...". This skill is how a full interactive session (where you have all tools) picks those up. This is the core of Ogma's two-surface workflow — see docs/workflow.md.

Where

  • Open tickets: ~/ogma/tickets/*.md
  • Resolved tickets: ~/ogma/tickets/done/
  • Each ticket is markdown with frontmatter (id, created, status, source) then a body.

(Adjust the path if you installed Ogma somewhere other than ~/ogma.)

Listing

Read ~/ogma/tickets/ (the top level only; ignore done/). For each open ticket show its id, age, and a one-line summary. If there are none, say so.

Working a ticket

  1. Read the full ticket. Confirm with the user which one to tackle if there are several.
  2. Do the work in this session (you have full tools here).
  3. When finished, resolve it:
    • Append a ## Resolution section to the ticket: what you did, the date, and any follow-up.
    • Set status: done in the frontmatter.
    • Move the file to ~/ogma/tickets/done/.
  4. Briefly tell the user what you did. If the fix changed how Ogma works (e.g. a new ogmactl subcommand or a relaxed permission), note that so the bot benefits next time.

Notes

  • Don't auto-resolve a ticket you only partially addressed — leave it open and note progress.
  • If a ticket is unclear, leave it open and ask the user (or message back via ~/ogma/bin/tg-send) for detail.

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.