scripts

Organize scripts into designated directories with cleanup and migration rules.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/tylermorganme/crop_plan_2025 --skill scripts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scripts
Source: https://github.com/tylermorganme/crop_plan_2025/tree/main/.claude/skills/scripts
Command: npx skills add https://github.com/tylermorganme/crop_plan_2025 --skill scripts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides clear guidelines for organizing and managing scripts across a codebase, reducing duplication and confusion when projects scale.

Core Features & Use Cases

  • Directory guidance: separate reusable tools under crop-api/scripts/, scratch work under tmp/, and portable skill scripts under .claude/skills/*/scripts/ to promote consistency.
  • Creation and cleanup rules: when to place new scripts, how to clean up temporary work, and how to migrate useful utilities into committed assets.
  • Use Case: a team standardizes script locations so a developer can quickly locate data-extraction utilities or test tools without duplicating logic.
  • Use Case: a maintainer exports a shared script from a project into a reusable skill script so it can run in other projects with minimal changes.

Quick Start

Start by auditing your repo to identify where your current scripts live, then move or copy core utilities into their designated locations following the guidelines above.

Frequently Asked Questions about scripts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to organize project scripts and reduce codebase duplication?

Organizing project scripts involves separating reusable tools under scripts/, scratch work in tmp/, and portable skill scripts in .claude/skills/*/scripts/ to reduce duplication. This standardizes locations so developers can quickly locate utilities without duplicating logic.

How do I structure reusable scripts so they are portable across multiple projects?

To make portable scripts across projects, place self-contained skill scripts in .claude/skills/*/scripts/ and apply clear separation rules. This ensures scripts run in other projects with minimal changes and are easy for contributors to follow.

Where should I put temporary scripts and scratch work in my development workflow?

Temporary scripts and scratch work belong in the tmp/ directory during development. You should apply cleanup rules to remove temporary work and migrate useful utilities into committed assets like crop-api/scripts/ for long-term maintenance.

When should I migrate temporary scripts into committed repository assets?

Migrate temporary scripts into committed assets when they become useful utilities, moving them from tmp/ into crop-api/scripts/ or .claude/skills/*/scripts/. This enforces conventions for self-contained scripts that are portable across projects and easy for contributors to follow.

Can I use standard directory conventions for scripts to help maintainers find data-extraction utilities?

Standard directory conventions help maintainers find data-extraction utilities by placing reusable tools in crop-api/scripts/ and portable skill scripts in .claude/skills/*/scripts/. Teams standardize script locations so a developer can quickly locate test tools without duplicating logic.