llama-farm/llamafarm / .claude/skills/temp-files
temp-files
VerifiedGuidelines for creating temporary files in system temp directory. Use when agents need to create reports, logs, or progress files without cluttering the repository.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.0 KB |
SKILL.md
View on GitHub---
name: temp-files
description: Guidelines for creating temporary files in system temp directory. Use when agents need to create reports, logs, or progress files without cluttering the repository.
allowed-tools: Bash, Write, Read
---
# Temporary Files Skill
When you need to create files to track progress, generate reports, or store temporary data, use the system's temporary directory instead of the repository root.
## Directory Structure
Use this base path for all temporary files (aligns with Claude Code's existing task output convention):
```
/tmp/claude/{sanitized-cwd}/
```
Where `{sanitized-cwd}` is the current working directory path with `/` replaced by `-` (leading slash stripped first to avoid a leading dash).
Example: Working in `/Users/bobby/workspace/pivot/llamafarm` → `/tmp/claude/Users-bobby-workspace-pivot-llamafarm/`
## Creating a Temp File
### Step 1: Create the directory
```bash
SANITIZED_PATH=$(echo "$PWD" | sed 's|^/||' | tr '/' '-')
REPORT_DIR="/tmp/claude/${SANITIZED_PATH}/reviews"
mkdir -p "$REPORT_DIR"
```
### Step 2: Generate a unique filename
Use this pattern: `{descriptor}-{YYYYMMDD-HHMMSS}.{ext}`
```bash
TIMESTAMP=$(date +%Y%m%d-%H%M%S)
FILENAME="code-review-${TIMESTAMP}.md"
FILEPATH="${REPORT_DIR}/${FILENAME}"
```
### Step 3: Write the file
Use the Write tool with the full temp path.
### Step 4: Inform the user
Always tell the user where the file was created:
> Report saved to: `/tmp/claude/Users-bobby-workspace-pivot-llamafarm/reviews/code-review-20260108-143052.md`
## When to Use This Pattern
- Code review reports
- Analysis outputs
- Progress tracking files
- Test result summaries
- Any generated documentation not explicitly requested in a specific location
## When NOT to Use This Pattern
- User explicitly specifies a file path
- Creating files that should be committed (e.g., README, config files)
- Editing existing files
## Cleanup Note
Files in `/tmp/` are cleared on system restart. If the user needs to preserve a file, suggest they copy it to a permanent location.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |