attach-content

Attach generated content to the current issue as a file.

1|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/Hunt-Gather-Create/_R1 --skill attach-content
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: attach-content
Source: https://github.com/Hunt-Gather-Create/_R1/tree/main/skills/attach-content
Command: npx skills add https://github.com/Hunt-Gather-Create/_R1 --skill attach-content

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically attach substantial content generated during a session to the current issue as a file, preserving it for future reference.

Core Features & Use Cases

  • Attach content to issues to preserve guides, reports, code, or documentation as attachments
  • Use cases include saving optimization notes, technical specs, or implementation checklists
  • Example: Attach a detailed analysis as a markdown file to the issue for team access

Quick Start

Generate the content you want to preserve and call attachContent with the full content, a descriptive filename, and an optional mimeType to attach it to the issue.

Frequently Asked Questions about attach-content

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I attach generated documentation to an issue as a file?▼

To attach documentation to an issue, use the attachContent tool with the content, a descriptive filename, and an optional mimeType to save it as a file attachment for team access.

What's the best way to preserve technical reports and guides on issues?▼

Preserving technical reports and guides is best done by attaching the generated content directly to the current issue as a file, ensuring substantial documentation remains accessible for future reference.

Can I save optimization notes and code as attachments to an issue?▼

Yes, you can save optimization notes and code as attachments by applying the attachContent tool, which stores the generated text as a file directly on the current issue.

Do I need to specify a mimeType when attaching content to issues?▼

You do not need to specify a mimeType to attach content to issues; it is an optional parameter used alongside the required content and filename to create the file attachment.

When should I use file attachments instead of inline text for issue content?▼

Use file attachments for issue content when storing substantial generated material like detailed analyses or implementation checklists, as attaching them as files preserves the content better than inline text.