AI agents often generate files that are hard to move across remote terminals, IDE sandboxes, browser sessions, and review tools. The public tflink-tmpfile skill.md gives agents a simple rulebook: upload a local artifact to tmpfile.link, return a temporary link, and keep the user aware of privacy and retention limits.
Table of Contents
Why Use a Skill File
A skill file turns a repeated workflow into durable instructions. Instead of telling an agent the upload endpoint, limits, response fields, and safety rules every time, you give it one stable URL:
https://tmpfile.link/skill.mdThat file tells the agent when to use tfLink, how to call the API, which response field to return, and what not to upload without explicit approval.
How the Agent Workflow Works
The flow is intentionally small. The agent checks the file, uploads it through the tfLink API, then returns the encoded download URL.
Install the Skill in an Agent or IDE
The exact folder depends on the tool, but the integration pattern is the same: create a skill folder and place the public instructions in a SKILL.md file.
Option A: reference the hosted skill
Use the tfLink temporary file sharing skill:
https://tmpfile.link/skill.mdOption B: save a local copy
mkdir -p ~/.agents/skills/tflink-tmpfile
curl -L https://tmpfile.link/skill.md \
-o ~/.agents/skills/tflink-tmpfile/SKILL.mdFor IDE assistants with project-local instructions, you can also add the same link to your workspace agent rules. Keep the hosted URL in the rule so future updates are easy to find.
Use It During Coding Work
Once the skill is available, prompts can stay short and concrete:
- "Upload this generated PDF and give me a temporary link."
- "Share the Playwright screenshot through tfLink."
- "Upload the failing CI log as a txt file and return the URL."
- "Create a zip of the repro assets, upload it, and mention the 7-day expiration."
The skill tells the agent to use multipart form data with the file field named file:
curl -X POST https://tmpfile.link/api/upload \
-F "file=@/absolute/path/to/artifact.zip"Agents should prefer downloadLinkEncoded in the response when it is present, because it is safe to paste into chats, markdown documents, and issue trackers.
Security Rules for Agents
Temporary links are still public-by-URL. A good agent should pause before uploading sensitive material and ask for confirmation when the content may include secrets or private data.
Do not upload without explicit approval
- API keys, passwords, private keys, cookies, and access tokens
- Production database dumps or customer data
- Documents containing regulated personal information
- Internal files the user has not asked to share
For anonymous uploads, the agent should also mention that files expire after 7 days. This expectation matters when a link is used in tickets, PR comments, or delayed review workflows.
Use Raycast Alongside IDE Agents
The Tflink Tmpfile Raycast extension is useful when the file or text is already in your macOS clipboard. IDE agents are better when the artifact lives inside a workspace or remote environment.
| Workflow | Best for |
|---|---|
| Raycast extension | Clipboard text, Finder files, quick desktop sharing, QR handoff |
| AI agent skill | Generated reports, screenshots, logs, archives, remote workspace artifacts |
Conclusion
The public skill.md file makes tfLink easy to reuse across AI coding agents and IDE assistants. It keeps the upload command, safety rules, response parsing, and retention note in one place, so the user can simply ask for a temporary link.