Skip to content
Agentmart
Submit a tool

firm-delivery-export

Post-processing skill for firm-orchestration: converts the structured JSON output of a multi-agent workflow run into real deliverables — GitHub Pull Requests…

Skill by romainsantoli-web

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/romainsantoli-web-firm-delivery-export

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Post-processing skill for firm-orchestration: converts the structured JSON output of a multi-agent workflow run into real deliverables — GitHub Pull Requests, Jira/Linear tickets, Markdown reports, project briefs or structured documents. Acts as the last-mile bridge between agent output and team tooling.

Use cases: documents, productivity, agent-building

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/firm-delivery-export

What's inside

Skill name
firm-delivery-export
Description
Post-processing skill for firm-orchestration: converts the structured JSON output of a multi-agent workflow run into real deliverables — GitHub Pull Requests, Jira/Linear tickets, Markdown reports, project briefs or structured documents. Acts as the last-mile bridge between agent output and team tooling.
License
MIT
Instructions
98 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# firm-delivery-export

Converts firm workflow output into **real deliverables** in team tooling.

## Supported formats

| Format | Target | Required env |
|---|---|---|
| `github_pr` | GitHub repository PR | `GITHUB_TOKEN` |
| `jira_ticket` | Jira issue | `JIRA_API_TOKEN` + `JIRA_BASE_URL` |
| `linear_issue` | Linear issue | `LINEAR_API_KEY` |
| `markdown_report` | Local file / chat | none |
| `structured_document` | Markdown with frontmatter | none |
| `project_brief` | Structured PDF-ready doc | none |
| `slack_digest` | Slack message via webhook | `SLACK_WEBHOOK_URL` |

## Usage (after firm-orchestration run)

```
Use firm-delivery-export to publish last workflow result as a GitHub PR:
  repo: "myorg/myrepo"
  branch: "ai/sprint-24-plan"
  title: "feat: Sprint 24 plan (AI-generated, human review pending)"
  reviewers: ["@john", "@sarah"]
```

## GitHub PR output schema

```json
{
  "format": "github_pr",
  "repo": "org/repo",
  "branch": "ai/{kebab-objective}",
  "base": "main",
  "title": "...",
  "body": "## AI-generated delivery\n\n{merged_output}\n\n---\n_Generated by firm-orchestration_",
  "draft": true,
  "reviewers": [],
  "labels": ["ai-generated", "needs-review"]
}
```

## Jira ticket output schema

```json
{
  "format": "jira_ticket",
  "project": "ENG",
  "issue_type": "Story",
  "summary": "...",
  "description": "{merged_output}",
  "priority": "Medium",
  "labels": ["ai-generated"],
  "components": []
}
```

## Security notes

- `GITHUB_TOKEN` must have `repo` scope — use fine-grained tokens scoped to target repo
- All PRs are created as **drafts** by default (`draft: true`) — never auto-merged
- Human review is mandatory: a `needs-review` label is applied unconditionally
- `JIRA_API_TOKEN` is never logged (masked in audit trail)
- Slack webhook URLs are treated as secrets (masked in JSONL audit)

## Error handling

| Error | Behavior |
|---|---|
| API rate limit | Retry with exponential backoff (3 attempts, max 30s) |
| Auth failure | Fail fast, output error to session, never retry |
| Network timeout | Fallback to `markdown_report` format locally |
| Invalid schema | Reject with validation error listing missing fields |

## Example with delivery pipeline

```
1. Run firm-orchestration:
   objective: "Document the payment service API"
   departments: ["engineering", "operations"]
   delivery_format: "github_pr"

2. Run firm-delivery-export automatically:
   → Creates draft PR "docs: Payment service API documentation"
   → Branch: ai/document-payment-service-api
   → Labels: ai-generated, needs-review, documentation
   → Assigns to @team-engineering for review
```

---

## 💎 Support

Si ce skill vous est utile, vous pouvez soutenir le développement :

**Dogecoin** : `DQBggqFNWsRNTPb6kkiwppnMo1Hm8edfWq`

From romainsantoli-web/setup-vs-agent-firm, MIT.

More from romainsantoli-web/setup-vs-agent-firm

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Feb 28, 2026 (8 months ago)
Last release
Mar 3, 2026 (7 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from romainsantoli-web

Cite this page

firm-delivery-export skill. Agent Mart. https://agentmart.dev/skills/romainsantoli-web-firm-delivery-export (last updated 2026-10-24)