Automated summary

Writes the body of a memloom pull request in a tight, enforced format: one opening sentence, bullets, and a short list of known gaps.

Strengths

Enforces a precise minimal structure (opening sentence, "What this adds", "Docs", "Known gaps")
Ships an explicit never-include list with the reason behind each exclusion
Gives concrete voice rules: plain short sentences, present tense, no em-dashes
Ends with a revision pass: reread and cut the weakest third

Limitations

Tightly coupled to the memloom repo and its /ship flow, not directly reusable elsewhere
Covers only the PR body, not branch setup or review
Its strict rules may clash with projects that want testing or design-rationale sections in the PR

When to use it

Use it whenever opening or editing a pull request body in the memloom repo, including from /ship.

When not to use it

Avoid it on projects that require verification, migration, or design-decision sections in their pull requests.

Security analysis

Safe

Quality score88/100

This is a pure prose style guide for writing PR descriptions. It declares no tools, contains no commands, no network or filesystem instructions, and asks for no secrets. The 'Never include' table is editorial guidance about content to omit from public PR text, not an instruction to hide security-relevant information from reviewers, so it carries no meaningful execution risk.

No concerns found

How this analysis is made

Examples

Open a PR after shipping a feature

/ship the budget-and-run branch and write the PR description using the pr-description skill.

Rewrite a bloated PR body

Rewrite this PR body with the pr-description skill: it currently has a test results section, commit counts, and a design rationale paragraph.

Describe a feature with known gaps

Write the memloom PR body for the new backlog budgeting feature. It does not support pausing mid-run yet, and the docs page is updated.

name: pr-description description: Write the PR description for a memloom pull request. Use whenever opening or editing a PR body in this repo, including from /ship.

Writing a memloom PR description

Name: Write a memloom PR description
Author: Skills Guide Bot

A PR describes the change to someone who was not in the room. It is public. Write only what a reader needs to understand what shipped and what it cannot do.

Shape

<one sentence: what the feature does>

## What this adds
- bullets

## Docs
<one short paragraph, only if docs changed>

## Known gaps
- one sentence each

Nothing else unless the change genuinely calls for it.

Rules

Open with one sentence. Not two. The second sentence is always a summary of the bullets below, which the reader is about to read anyway.

Bullets, not tables. A table looks organised and reads slower. Bold the subject of each bullet and follow it with the fact.

Every line earns its place. Before keeping a sentence, ask what the reader does differently for having read it. If the answer is nothing, cut it.

Known gaps are one sentence each. State the limitation, not the history or the plan.

Never include

| Never | Why | |---|---| | A verification or testing section | Tests passing is the default. Nobody reads "686 tests green" | | What the code review found | Internal. The reader cares what the code does now, not what it did on Tuesday | | Migration or repair steps for a dev store | Internal. Say it in chat, never in public | | Commit counts, file counts, line counts | GitHub already shows these | | Rationale for design decisions | That belongs in code comments | | Anything phrased as effort or process | "This was tricky", "after several iterations" |

Voice

Plain short sentences. No em-dashes, no middle dots. Present tense. Name the thing rather than describing it: "Set a budget and a run keeps going until the backlog is clear" beats "a configurable budget mechanism has been introduced".

Before posting

Read it back and delete the weakest third. It will still say everything that matters.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/write-a-memloom-pr-description-mse7in39/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/write-a-memloom-pr-description-mse7in39' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/write-a-memloom-pr-description-mse7in39/download' --output '.skill-downloads/write-a-memloom-pr-description-mse7in39/SKILL.md.part' && mv '.skill-downloads/write-a-memloom-pr-description-mse7in39/SKILL.md.part' '.skill-downloads/write-a-memloom-pr-description-mse7in39/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code

test -f '.skill-downloads/write-a-memloom-pr-description-mse7in39/SKILL.md' && test -s '.skill-downloads/write-a-memloom-pr-description-mse7in39/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/pr-description' && cp -R '.skill-downloads/write-a-memloom-pr-description-mse7in39' '.claude/skills/pr-description'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation

openskills install './.skill-downloads/write-a-memloom-pr-description-mse7in39'

openskills read 'write-a-memloom-pr-description-mse7in39'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/write-a-memloom-pr-description-mse7in39/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

Supabase Docs Authoring

Documentation

Write, edit, and review Supabase documentation content including guides, tutorials, reference docs, and partials. Follow style guides and MDX/TOML validation rules.

Claude CodeintermediateSafe 108,544

Skills Guide Bot