agentleFS
Sign inStart free
sonichisonichi/sutando/skills/open-sutando-ref/SKILL.md

open-sutando-ref

Skill396 starsChanged 6 months agoMITView on GitHub

Resolve a fuzzy GitHub reference (issue number, PR number, or text description) to a URL and optionally open it in the browser.

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:

    If --open flag is present, call open <url> to navigate in the default browser.

    line 30

≈ “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

Open Sutando Ref

Resolves natural-language and numeric GitHub references to URLs and optionally navigates to them. Closes #903.

Usage: /open-sutando-ref [--open] <ref>

ARGUMENTS: $ARGUMENTS

Reference formats

  • #874 / 874 — numeric (auto-detects PR vs issue)
  • PR 874 / pull request 874 — explicit PR
  • issue 874 — explicit issue
  • "the result-marker PR" — fuzzy text search via gh pr/issue list --search
  • "multi-core scheduler" — searches both PRs and issues, returns best match

What this skill does

  1. Parse the reference: numeric, explicit PR/issue, or fuzzy query.
  2. For numeric refs: check whether the number exists as a PR, fall back to issue.
  3. For fuzzy refs: run gh pr list --search <query> then gh issue list --search <query>; return the top match URL.
  4. Print the URL to stdout.
  5. If --open flag is present, call open <url> to navigate in the default browser.

Configuration

  • SUTANDO_GH_REPO — override the target repo (default: inferred from gh repo view or sonichi/sutando).

When to use

  • Voice command: "open the result-marker PR" → invoke resolve.py --open "result-marker PR"
  • Chat shorthand: "check #874" → invoke resolve.py "#874"
  • Proactive loop step 10: when forwarding Discord references, resolve before posting

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.

Check your setup, free