Rename Batch Plan

Overview

You pass a list of file names (not paths) and optional normalization rules; we return a deterministic side-effect-free rename plan with per-file targets, reason codes, and collision detection. We reject path traversal in names and compile removeCharacters regexes on a linear-time engine. We never rename files on disk. Do not use this when you need to apply renames — only to preview them.

Agents should preview renames and catch collisions before touching files on your side.

When to use it

Scope

Non-goals

• Does not rename files on disk
• Does not accept directory paths in the files list
• Does not use Java backtracking regex on caller patterns

Properties

Capabilities

Cost & billing

Flat rate per invocation

File handling

How we handle your data

Input schema

Output schema

API contract

curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"file.rename_batch_plan","input":{"files":["A File.TXT"],"rules":{"case":"lower"}}}'

import { Squillify } from "@squillify/sdk";

const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });

const { output } = await sq.execute("file.rename_batch_plan", {"files":["Report Final (1).PDF"],"rules":{"spaces":"dash","removeCharacters":"[^a-zA-Z0-9._ -]","extensionCase":"lower","case":"lower"}});

Errors

Other limits

Limitations

• Does not rename files on disk
• Does not accept directory paths in the files list
• Does not use Java backtracking regex on caller patterns
• Actually renaming files (out of scope for this skill)
• Path-based moves or directory restructuring

How to call

POST /v1/execute (requires authentication)

{
  "skillKey": "file.rename_batch_plan",
  "input": {
    "files": [
      "Report Final (1).PDF"
    ],
    "rules": {
      "spaces": "dash",
      "removeCharacters": "[^a-zA-Z0-9._ -]",
      "extensionCase": "lower",
      "case": "lower"
    }
  }
}

Examples

{
  "files": [
    "Report Final (1).PDF"
  ],
  "rules": {
    "spaces": "dash",
    "removeCharacters": "[^a-zA-Z0-9._ -]",
    "extensionCase": "lower",
    "case": "lower"
  }
}

{
  "collisions": [],
  "safeToApply": true,
  "plan": [
    {
      "changed": true,
      "target": "report-final-1.pdf",
      "reasonCodes": [
        "CHARACTER_REMOVED",
        "SPACE_REPLACED",
        "CASE_CHANGED",
        "EXTENSION_CASE_CHANGED"
      ],
      "source": "Report Final (1).PDF"
    }
  ]
}

{
  "files": [
    "File.txt",
    "FILE.txt"
  ],
  "rules": {
    "case": "lower"
  }
}

{
  "collisions": [
    {
      "source": "FILE.txt",
      "target": "file.txt",
      "reason": "Target name collides with an earlier target (case/unicode-insensitive)."
    }
  ],
  "safeToApply": false,
  "plan": [
    {
      "changed": true,
      "target": "file.txt",
      "reasonCodes": [
        "CASE_CHANGED"
      ],
      "source": "File.txt"
    },
    {
      "changed": true,
      "target": "file.txt",
      "reasonCodes": [
        "CASE_CHANGED"
      ],
      "source": "FILE.txt"
    }
  ]
}

Recommended use cases

• Preview a bulk rename before an apply step you control
• Normalize filenames and catch case or Unicode collisions
• Strip unsafe characters with a bounded regex

Avoid for

• Actually renaming files (out of scope for this skill)
• Path-based moves or directory restructuring

Related skills

Composable with

Safety & privacy

• Runs without calling any external service.
• Your payloads are never stored permanently.
• Telemetry captures metadata only — never your payload contents.
• We never train models on your payloads.
• No human reviews your payloads.

Tags