Skip to content
Skills Library
Other · Writing

ids

/ids

Corrects output that refers to entities by bare identifier, restating it with a human-readable label beside every ID, and keeps that rule for the rest of the conversation. Use when the user invokes `/ids` or `$ids`, or complains that bead IDs, PR numbers, commit SHAs, or ticket keys were given without titles.

Repository
ai-config ↗
Licence
GPL-3.0
Last repository change
08.10.2026

Assessment and security

96/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content31 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 08.10.2026, without references to retired models or APIs.

Licence

GPL-3.0, otwarta.

What it does and when to use it

Corrects output that refers to entities by bare identifier, restating it with a human-readable label beside every ID, and keeps that rule for the rest of the conversation. Use when the user invokes `/ids` or `$ids`, or complains that bead IDs, PR numbers, commit SHAs, or ticket keys were given without titles.

Original author description

Corrects output that refers to entities by bare identifier, restating it with a human-readable label beside every ID, and keeps that rule for the rest of the conversation. Use when the user invokes `/ids` or `$ids`, or complains that bead IDs, PR numbers, commit SHAs, or ticket keys were given without titles.

How it works

SKILL.md has no level-two headings · 31 lines, 244 words

SKILL.md preview
---
name: ids
description: >-
  Corrects output that refers to entities by bare identifier, restating it
  with a human-readable label beside every ID, and keeps that rule for the
  rest of the conversation. Use when the user invokes `/ids` or `$ids`, or
  complains that bead IDs, PR numbers, commit SHAs, or ticket keys were given
  without titles.
---

# Label every ID

You referred to one or more entities (beads issues, GitHub issues, pull
requests, commits, tickets, files, jobs, etc.) by bare identifier alone. Bare
IDs are opaque to humans: `ai-config-a1b2c3` or `#4271` conveys nothing
without a lookup.

Restate what you just said, giving every entity reference a short
human-readable label alongside its ID. Look up the title if you don't already
have it. Examples of the required form:

- `ai-config-a1b2c3 (prefix parallel subagent labels with the bead ID)`
- `PR #4271 (fix race in worktree cleanup)`
- `fea0177 (feat(beads): prefix parallel subagent labels with the bead ID)`

Keep the label short: a title or a few-word summary, not a paragraph. The ID
stays, because it is what commands take as arguments; the label is what makes
the sentence legible.

**This applies for the rest of this conversation, not just to the message you
are correcting.** Every subsequent mention of an entity, in prose, in lists,
in summaries, in handoffs, must carry its label. The first mention in a
message always needs one; repeated mentions in the same immediate context may
use the bare ID once the label is established.

**Do not treat this invocation as a signal to record a new memory or amend
existing guidance.** Most likely the guidance already exists and the failure
was not following it. Adding more instructions on top of instructions you
already had does not fix that. Just fix the output and keep it fixed.

Versions

The database has no other skills named ids.

Database snapshot: 13.11.2026 · package version fbc55ea4af27 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

No similar skills in the database.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.