More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Clean Landing: Safe Deploys From Windows to Linux

    1

    Stop deploys from Windows breaking your Linux server or leaking files. A bundled script finds CRLF scripts, secrets and working files before you ship, and your agent fixes them.

    Free

    Security scanned
    Clean Landing: Safe Deploys From Windows to Linux

    Clean Landing: Safe Deploys From Windows to Linux

    Example session with this skill installed

    I deploy from Git Bash with tar. deploy.sh just died with set: pipefail: invalid option name, and I'm about to push this folder into my web root.

    • Read your context and instructions
    • Compiled the clean landing

    Summary

    Windows line endings broke deploy.sh. Linux bash reads pipefail with a carriage return attached and rejects the option. Hold the push: the checker also found your .env and two working files that would land in the web root. I tested the fix on a copy, so your files haven't changed.

    Checker output

    CRLF in 2 Linux-bound file(s):
      cron.d/backup
      deploy.sh
    WARNING: no .gitattributes in this folder.
    Should not be deployed (1):
      .env
    Working files in a public folder (2):
      deploy.sh
      notes.md
    FAILED
    

    What I found

    FoundRiskFix
    deploy.sh has CRLFLinux bash fails on set -euo pipefailStrip \r with sed
    cron.d/backup has CRLFCron hits the same carriage returnsStrip \r, install it outside the web root
    No .gitattributesWindows checkouts can bring CRLF backCommit the rules from the skill
    .envVisitors could download your secretsLeave it out of the tar
    deploy.sh, notes.mdVisitors could read your internal filesLeave them out of the tar

    Commands

    cd demo-deploy && sed -i 's/\r$//' deploy.sh cron.d/backup && file deploy.sh cron.d/backup
    tar czf ../site.tgz index.html && tar tzf ../site.tgz
    mkdir ../staged && tar xzf ../site.tgz -C ../staged
    python -I <skill-folder>/scripts/predeploy_check.py ../staged --public
    

    Add your CSS, JS and images to the tar list. On my copy, file showed no CRLF left and the staged folder returned OK. It still printed the .gitattributes warning, which you can ignore for a folder of site files. Run --public on the staged folder, because the project folder keeps failing while it holds .env and deploy.sh.

    Next steps

    1. Check the server. If the script stopped before its restart step, you have new files on disk and old code in memory.
    2. Run the same sed on the server's copy, then rerun the deploy.
    3. If this folder is a Git repo, commit .gitattributes and run git add --renormalize .. Your working files stay CRLF until Git rewrites them. I didn't test this step, because the demo folder has no repo.
    4. Use file to check line endings before you deploy. A CRLF test script ran in Git Bash here with no error, so a clean local run tells you nothing about Linux.
    5. If .env ever reached a web root, rotate those secrets and purge your CDN.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    A tar from Windows can ship scripts that stop your deploy halfway, or put your .env in a public folder.

    Your agent will

    • Run a checker that lists CRLF files, secrets and working documents
    • Fix line endings for good with a .gitattributes, including the working files --renormalize leaves behind
    • Build an explicit deploy list and read the archive before it ships
    • Add nginx rules that block dotfiles and working files
    • Test with the right Host header and read the body, because a 200 proves nothing on a site with a fallback page

    How it was tested

    We ran the checker on real projects and on samples built to fail, and an independent review tested the Git steps.

    Pattern matching can flag files that really do ship. Use --allow for those.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 8 days ago

    • Free with an Agensi account

    Requires

    Python 3 for the checker
    Git

    Permissions

    Terminal / Shell
    Read Files

    File Scopes

    ./**

    The checker reports file names only and makes no network calls.

    Listed8 days ago

    What's inside

    Frequently Asked Questions

    The checker only reports. Your agent makes fixes when you agree.

    No, though the permanent fix uses .gitattributes.

    Yes. Run the checker on whatever you're about to send.

    New in DevOps & Cloud