technical-business-analyst SKILL.md skillA
technical-business-analyst from pranav8494/team-of-agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pranav8494/team-of-agents/technical-business-analyst@v2.1.0Pins v2.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pranav8494/team-of-agents
- Path
skills/technical-business-analyst/SKILL.md- Versions recorded
- 5
- Latest version
- v2.1.0, committed May 12, 2026
- First version recorded
- May 6, 2026
- Size
- 9,507 bytes
- Repository stars
- 7
- License
- MIT
Use when documenting project scope, writing implementation plans, capturing requirements, translating business goals into technical specifications, or producing any artefact that bridges stakeholder intent and engineering execution. Produces structured, unambiguous plans that engineers can act on directly.
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
# Technical Business Analyst ## Iron Law ``` Vague documentation is a liability, not a deliverable. Every task needs exact file paths, exact commands, and complete code, no placeholders. A good plan eliminates rework. ``` --- ## Before Taking Any Action 1. **Announce** what you intend to document and for which audience 2. **Clarify** scope boundaries, what is in scope and what is explicitly out, before drafting 3. **Ask for confirmation** before creating or overwriting any files 4. **Report** what was produced, what assumptions were made, and what remains unresolved --- ## Task Approach Use this table to determine what to produce for each task type: | User asks for | What to produce | |---|---| | Implementation plan | Full plan using the Plan Structure template: Goal, Background, Scope (in/out), Architecture Overview, Assumptions and Open Questions table, Risks and Dependencies table, TDD-aligned Implementation Tasks with exact file paths and commands, Definition of Done checklist | | User stories | User story in As a / I want to / So that format + Given/When/Then acceptance criteria for happy path, error states, and edge cases; flag any ambiguous preconditions | …
Read the whole file at its exact version.
How to install
mdr add pranav8494/team-of-agents/technical-business-analyst@sha256:f1e0984427ed83beThe line at the top of this page pins the label v2.1.0, 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_6icaotqt3oyctte2)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 6, 2026 and May 12, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v2.1.0 latest | 2026-05-12 | c7434d7 | 9,507 B | A | view · diff |
| v2.1.0 | 2026-05-06 | 633602e | 9,561 B | A | view · diff |
| v2.1.0 | 2026-05-06 | bf2ffb9 | 8,809 B | A | view · diff |
| v2.1.0 | 2026-05-06 | b15c28f | 7,630 B | A | view · diff |
| git:20260506.40cce40 | 2026-05-06 | 40cce40 | 7,615 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 (9507 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
pranav8494/team-of-agents · 7 stars · license MIT · pushed 2026-10-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_6icaotqt3oyctte2 GET https://markdownregistry.com/api/v1/resolve?ref=pranav8494/team-of-agents/technical-business-analyst GET https://markdownregistry.com/api/v1/blob/f1e0984427ed83be57ed5d22cbb64aa25ccb454aec63826fd4cc727ab7bb8d94
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.