agentleFS
Sign inStart free
adampoitadampoit/ai/skills/chatgpt-share-markdown/SKILL.md

chatgpt-share-markdown

Skill2 starsChanged 13 days agoMITView on GitHub

Convert public ChatGPT share links into clean Markdown transcripts for agent context. Use when a user provides a https://chatgpt.com/share/... URL and wants the conversation summarized, archived, or reused as input context.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run the script with a public chatgpt.com/share/...

    line 16
  2. Distinctive:

    Use the Markdown directly as context, or trim it to only the relevant turns.

    line 18
  3. Very specific:

    If the URL is not a public share link, request https://chatgpt.com/share/....

    line 50
  4. Distinctive:

    If parsing fails, rerun once.

    line 51
  5. Distinctive:

    If output looks incomplete, keep the parser output and supplement manually only for missing turns.

    line 52

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Chatgpt Share Markdown

Convert shared ChatGPT conversations into role-labeled Markdown using ./scripts/chatgpt-share-markdown.cs.

dotnet run --file ./scripts/chatgpt-share-markdown.cs -- "https://chatgpt.com/share/<id>"

Workflow

  1. Run the script with a public chatgpt.com/share/... URL.
  2. Inspect the generated Markdown for media placeholders and formatting.
  3. Use the Markdown directly as context, or trim it to only the relevant turns.

Commands

Export to stdout:

dotnet run --file ./scripts/chatgpt-share-markdown.cs -- "https://chatgpt.com/share/<id>"

Export to a file:

dotnet run --file ./scripts/chatgpt-share-markdown.cs -- "https://chatgpt.com/share/<id>" --output "/tmp/chat-context.md"

Output

  • Conversation title as H1
  • Metadata block with source URL and optional update timestamp/model
  • One section per turn: ## User and ## Assistant by default (## Tool optional)
  • Markdown-friendly content with fenced code blocks and basic multimodal placeholders
  • Internal tool-action payloads and reasoning recaps are omitted by default to keep context clean

Optional flags:

--include-tool-turns --include-internal-actions --include-reasoning

Troubleshooting

  • If the URL is not a public share link, request https://chatgpt.com/share/....
  • If parsing fails, rerun once; share page payload shape can change.
  • If output looks incomplete, keep the parser output and supplement manually only for missing turns.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free