feat-issue SKILL.md skillA

feat-issue from thinkflowlab/opendirector is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add thinkflowlab/opendirector/feat-issue@git:20261031.447e07d

Pins git:20261031.447e07d in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
thinkflowlab/opendirector
Path
.agents/skills/feat-issue/SKILL.md
Versions recorded
2
Latest version
git:20261031.447e07d, committed Oct 31, 2026
First version recorded
Oct 26, 2026
Size
6,993 bytes
Repository stars
412
License
Apache-2.0

Plan a OpenDirector feature and publish a concise, actionable GitHub Issue through gh CLI. Use when the user invokes feat-issue or requests feature planning with issue creation, not for implementation or discussion of the skill itself.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Feat Issue

Turn a feature request into a focused specification stored as a remote
GitHub Issue. Keep the feature document in memory and publish through gh
CLI; do not save it as a local Markdown file, including a temporary file.
The skill's own files remain repository-local.

## Invocation and scope

- Explicit invocation authorizes planning and creating the feature Issue.
  Use the feature details supplied in the current conversation. If no
  feature can be identified, ask what to plan before creating anything.
- A request to create or edit this skill, discuss its design, or draft a
  document without publishing does not authorize an Issue. Honor explicit
  preview-only or no-publish instructions.
- An implicitly selected skill may publish when the request includes Issue
  creation. Do not silently expand a planning-only request into publishing.
- Once publication is authorized and the target is clear, create the Issue
  without another confirmation round. Normal execution permissions apply.
- This workflow does not implement code, stage files, commit, create a
  branch or PR, or change existing Issues unless separately requested.

## Plan the feature
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_qs3mdcsfskckvqq6/3c9bbf2c3f2bcdbbc7b1de185ae3529f95984f84e4e36fd6ee6bc2619bcbd104.json

Then /plugin install feat-issue@markdownregistry-qs3mdcsfskckvqq6 in Claude Code. It installs git:20261031.447e07d, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add thinkflowlab/opendirector/feat-issue@sha256:3c9bbf2c3f2bcdbb

The line at the top of this page pins the label git:20261031.447e07d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_qs3mdcsfskckvqq6.svg)](https://markdownregistry.com/a/art_qs3mdcsfskckvqq6)

4 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in thinkflowlab/opendirector/feat-issue since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of feat-issue from somewhere else? Ask it: where did my feat-issue come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 2 versions of this file, between Oct 26, 2026 and Oct 31, 2026, about one every 5 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261031.447e07d latest2026-10-31 447e07d 6,993 BA view · diff
git:20261026.2bb74042026-10-26 2bb7404 6,985 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (6993 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

thinkflowlab/opendirector · 412 stars · license Apache-2.0 · pushed 2026-11-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_qs3mdcsfskckvqq6
GET https://markdownregistry.com/api/v1/resolve?ref=thinkflowlab/opendirector/feat-issue
GET https://markdownregistry.com/api/v1/blob/3c9bbf2c3f2bcdbbc7b1de185ae3529f95984f84e4e36fd6ee6bc2619bcbd104

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from thinkflowlab/opendirector

bug-issue SKILL.md skill
thinkflowlab/opendirector · .agents/skills/bug-issue/SKILL.md · Reproduce and verify a reported OpenDirector bug, then publish an evidence-based GitHub Bug Issue. Use when the user…
git:20261031.447e07d · audit A · 412 stars
git-commit SKILL.md skill
thinkflowlab/opendirector · .agents/skills/git-commit/SKILL.md · Create a OpenDirector Git commit, or draft its message, from the current staging area only. Inspect git diff --staged…
git:20261102.0df33fa · audit A · 412 stars
install-opendirector SKILL.md skill
thinkflowlab/opendirector · .agents/skills/install-opendirector/SKILL.md · Install OpenDirector from source on the current machine. Detect the platform, check and install missing prerequisites…
git:20261105.6c83d43 · audit B · 412 stars
opendirector-review SKILL.md skill
thinkflowlab/opendirector · .agents/skills/opendirector-review/SKILL.md · Review one OpenDirector pull request tip and report PASS, WITHHOLD, or REQUEST CHANGES. Use when the user invokes…
git:20261110.f931f1a · audit A · 412 stars
AGENTS.md AGENTS.md file
thinkflowlab/opendirector · AGENTS.md
git:20261107.93e84c4 · audit A · 412 stars
character-replacement SKILL.md skill
thinkflowlab/opendirector · packages/agent/skills/character-replacement/SKILL.md · Plan MiniMax-H3 character replacement, write per-segment Ref2VA prompts and configure reusable H3-04 ComfyUI workflows…
git:20261102.284ee2d · audit A · 412 stars

Every file in thinkflowlab/opendirector

Browse by kind, by grade A, or by owner.

Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.