developer-feedback-loop SKILL.md skillA
developer-feedback-loop from samber/developer-relations-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add samber/developer-relations-skills/developer-feedback-loop@v1.0.1Pins v1.0.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- samber/developer-relations-skills
- Path
skills/developer-feedback-loop/SKILL.md- Versions recorded
- 5
- Latest version
- v1.0.1, committed Oct 21, 2026
- First version recorded
- Oct 21, 2026
- Size
- 19,846 bytes
- Repository stars
- 8
- License
- MIT
Designs the loop carrying developer feedback from Discord, Slack, forums, support, GitHub issues, sales calls and events to product and back - one record of truth, dedup rules, records product acts on, product-owned decisions, public status replies including the no, and loop metrics. Use whenever feature requests pile up in the community and product never sees them, or someone asks how DevRel should hand feedback to product, close the loop with developers, triage feature requests across…
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
# Developer Feedback Loop You design how developer feedback travels from wherever developers say it to the people who decide what gets built, and back to the developers who asked. The usual complaint is "product never sees what the community asks for". The cause is rarely a missing tool. It is three gaps: nobody on the product side agreed to receive and decide, requests arrive as solutions with no evidence, and nobody owns telling the requester what happened. Design around those three, in that order. The loop makes three promises. Every request is captured once. Every captured request gets a decision. Every requester hears the decision, including when it is no. Stay out of neighbouring jobs: - The issue queue itself, labels for bugs, stale policy: samber/developer-relations-skills@oss-issue-triage - Community health metrics: samber/developer-relations-skills@developer-community-health - DevRel's company-wide KPIs: samber/developer-relations-skills@devrel-metrics - Writing the release note a shipped request links to: samber/developer-relations-skills@changelog-writing - Who the segments are: samber/developer-relations-skills@developer-segmentation …
Read the whole file at its exact version.
How to install
mdr add samber/developer-relations-skills/developer-feedback-loop@sha256:fb9f9f0ce12295fdThe line at the top of this page pins the label v1.0.1, 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.
[](https://markdownregistry.com/a/art_gz2nkvylgz72miu2)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, all committed on Oct 21, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.1 latest | 2026-10-21 | 4c9f4e3 | 19,846 B | A | view · diff |
| v1.0.0 | 2026-10-21 | 41d83c4 | 19,846 B | A | view · diff |
| v1.0.0 | 2026-10-21 | d18c14c | 19,645 B | A | view · diff |
| v1.0.0 | 2026-10-21 | eef6b20 | 19,499 B | A | view · diff |
| v1.0.0 | 2026-10-21 | dbff509 | 19,347 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (19846 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
samber/developer-relations-skills · 8 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gz2nkvylgz72miu2 GET https://markdownregistry.com/api/v1/resolve?ref=samber/developer-relations-skills/developer-feedback-loop GET https://markdownregistry.com/api/v1/blob/fb9f9f0ce12295fd7d2dc9057d24966e676beca38bf0e6f853d1df9ca06a620c
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.