agentleFS
Sign inStart free
roee-hershroee-hersh/toolpass/.claude/skills/new-issue/SKILL.md

new-issue

Skill4 starsChanged 44 days agoApache-2.0View on GitHub

Write and open a well-scoped GitHub issue for toolpass (an integration, a feature, a good first issue or a bug). Use when asked to open, draft or suggest issues.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. richkuo/rk-skills★ 50same name
    2. YUVARAJ-R-ai/my-claude-skills★ 2same name
    3. wiseiodev/skills★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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. Distinctive:

    Search open and closed issues for duplicates.

    line 12
  2. Very specific:

    Read the parts of the repo the issue touches, so every name in the issue is real: action names from toolpass catalog <integration>, …

    line 13
  3. Distinctive:

    Keep it short enough to read in a minute.

    line 38

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

Writing a toolpass issue

Argument: the idea, e.g. /new-issue Linear integration or /new-issue 3 good first issues.

Before writing

  1. Search open and closed issues for duplicates. If one exists, link it instead of opening a new one.
  2. Read the parts of the repo the issue touches, so every name in the issue is real: action names from toolpass catalog <integration>, resource forms from docs/integrations/<name>.md, file paths that exist. Never invent an API endpoint; if unsure how the vendor exposes something, say so in the issue.
  3. For a batch ("3 good first issues"), pick work that is small, self-contained and useful now (docs, examples, tests, a missing action), not the hardest items on the roadmap.

Shape

Title: Integration: <Product>, or an imperative summary (Helm chart, Example: calling toolpass from an MCP tool).

Body, in this order, leaving out sections that do not apply:

  • Goal: one or two sentences on the question toolpass should answer or the thing a user gets ("may this user acknowledge incidents on this service").
  • How: the vendor API calls that answer it for a named user, and how the email maps to the vendor's identity. Say which cases must be unknown (conditions, missing scopes, info the credential cannot see); deny only when the system positively says no.
  • Credential: the read-only credential and the minimum scopes, and what a narrower credential cannot see.
  • Resources: the type:id forms and the actions, following existing integrations' naming.
  • Scope for non-integration work: a short bullet list of what is in and what is out.
  • A link to docs/development/integration-authoring.md for integrations: docs page, fake-upstream tests, vendor API description in test/specs/fetch.sh.
  • For roadmap integrations, a line linking the epic (#19).

Keep it short enough to read in a minute. No marketing language.

Labels

  • integration for a new system; good first issue + help wanted for small, well-scoped work a newcomer can finish without deep context; bug for defects.

Opening

Open the issue with the GitHub tools (not a local file), end the body with the Claude Code attribution footer, and reply with the issue link and a one-line summary per issue.

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