file-naming
Analyze file content and propose intelligent renames using context-aware naming conventions. Date-prefixed for transactional/periodic documents, content-first for creative works. Use for organizing files, cleaning up downloads, or standardizing filenames.
What this skill does
# Rename Files Analyze files and propose intelligent renames based on content type and metadata. Provide: a single file path, list of file paths, or folder path. ## Naming Conventions ### Transactional/Periodic Documents **Repetitive transactions** (orders, receipts, invoices, appointments): - Format: `YYYY-MM-DD Category Type - Details.extension` - Example: `2025-06-13 Amazon Order 123-456 - USB Cable.pdf` - Include: dates, entity names, order/invoice numbers, item descriptions **Periodic documents** (statements, bills, forms): - Format: `YYYY-MM Type - Entity.extension` - Example: `2025-06 Bank Statement - Chase Checking.pdf` - Example: `2023-12 W2 - Acme Corp.pdf` **Ongoing agreements** (contracts, policies): - Format: `YYYY-MM Type - Entity.extension` - Example: `2025-01 Service Agreement - Internet Provider.pdf` **Appointments/visits**: - Format: `YYYY-MM-DD Type - Provider/Location.extension` - Example: `2025-06-13 Dental Visit - Dr Johnson.pdf` ### Creative/Project Files **Date as supplementary** (photos, projects, creative work): - Format: `Description - Date.extension` or `Description - Context Date.extension` - Example: `Vacation Photos - Hawaii 2025.jpg` - Example: `Website Redesign - Draft 2025-06.pdf` - Example: `Company Logo 2025.png` **Evergreen content** (manuals, references): - Format: `Type - Name/Description.extension` - Example: `Product Manual - Widget Pro.pdf` ## Key Principles - **ISO 8601 dates**: YYYY-MM-DD (specific dates) or YYYY-MM (monthly/annual) - **Date placement**: Start for time-critical sorting; end for contextual info - **Remove**: Technical metadata (1080p, WEB-DL), problematic characters (`:*?"<>|#%&`) - **Keep**: Scannable and sortable filenames ## Process 1. Analyze files using OCR, text extraction, vision analysis, filename patterns 2. Build the complete rename plan before taking any action 3. Validate the plan: if any file cannot be mapped to a destination name, stop and report — do not proceed with partial results 4. Validate the plan: confirm no two files share a destination name — if any collision exists, stop and report 5. Present preview table: "Original Filename" | "New Filename" (show up to 15 files if many present; note any that couldn't be analyzed) 6. Wait for confirmation before executing 7. Execute using no-clobber semantics — never overwrite an existing file; if a collision occurs at execution time, halt immediately If content unclear: make best guess from filename, clean up existing name, or leave unchanged with note. **For TV show files**, see [references/tv-episodes.md](references/tv-episodes.md) for Plex/media manager naming conventions.
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.