[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F0TQ2Z0PWG8CX5AXR05G2C":3,"skill-same:01M7F0TQ2Z0PWG8CX5AXR05G2C":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7F0TQ2Z0PWG8CX5AXR05G2C","setup-storage",null,"Use when configuring where evidence is replicated — walks through defining a storage remote, confirms its retention or write-once behaviour, and records the destination policy without ever touching credentials. Triggers - \"set up evidence storage\", \"configure the rclone remote\", \"where should evidence be backed up\".","shotcowboystyle\u002Fag-skills","shotcowboystyle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62471?v=4","01M7EZTCFCZJ6K3MYW8BPM4X6R","Curtis Blanton","01M7EZTCG1S5M04J90A931X9BX",0,"MIT","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fevidence-ops\u002Fskills\u002Fsetup-storage\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: setup-storage\ndescription: Use when configuring where evidence is replicated — walks through defining a storage remote, confirms its retention or write-once behaviour, and records the destination policy without ever touching credentials. Triggers - \"set up evidence storage\", \"configure the rclone remote\", \"where should evidence be backed up\".\nallowed-tools: Bash(rclone *), Bash(aws *), Bash(command *), Bash(mkdir *), Read, Write\n---\n\n# Set Up Storage\n\nDefine where verified evidence is replicated, and confirm that the destination actually\nresists rewriting before anything is trusted to it.\n\n## When to use\n\n- During onboarding, once the local pipeline works.\n- Adding a second, independent destination.\n- Auditing whether an existing destination really is immutable.\n\n## Procedure\n\n### 1. Choose the protection model\n\nAsk which of these applies, because they fail differently:\n\n- **Object storage with a retention lock** — S3 Object Lock or an equivalent. Objects\n  cannot be deleted or overwritten until their retention expires. Requires versioning\n  on the bucket. Since November 2023 S3 can enable Object Lock on an existing bucket, so\n  a new bucket is not required; objects already in it are not locked until a retention\n  is set on each.\n- **Append-only or immutable-tier storage** — provider-enforced, no client cooperation\n  needed.\n- **Physical write-once media** — an optical disc or a WORM cartridge. Immutable by\n  construction, offline by default, and slow to recover from.\n- **An ordinary remote** — no protection at all. Usable as a second copy, but must not\n  be described as immutable.\n\nBe direct if the chosen destination provides no protection. An ordinary bucket with\ncareful habits is not immutable storage.\n\n### 2. Define the remote\n\nCreate the remote non-interactively, with credentials taken from the environment or the\nAWS credential chain rather than stored in the remote:\n\n```bash\nrclone config create \"$REMOTE\" s3 provider=AWS env_auth=true region=\"$REGION\" --non-interactive\nrclone listremotes\n```\n\nDo not run bare `rclone config`: it is an interactive wizard that prompts for access\nkeys. Never ask for a secret in conversation, never echo one, and never write one into\nthe workspace. If no credentials are available in the environment, stop and tell the\nuser to set them up themselves (for example `aws configure` in their own terminal).\n\n### 3. Confirm the bucket's actual settings\n\n```bash\naws s3api get-bucket-versioning --bucket \"$BUCKET\"\naws s3api get-object-lock-configuration --bucket \"$BUCKET\"\n```\n\nReport what these return rather than what was intended. An empty or missing\nObject Lock configuration means no lock, whatever the bucket was meant to have. Object\nLock can be enabled on an existing bucket (versioning must be on first), but that is a\nchange to the user's storage: state it and get agreement before running\n`put-object-lock-configuration`. Check, do not assume.\n\nNote which retention mode is configured. Governance mode can be bypassed by a\nsufficiently privileged user; compliance mode cannot be bypassed by anyone, including\nthe account root, until retention expires. That difference is the whole point, and it\nis also irreversible — say so before anyone chooses compliance mode.\n\n### 4. Test with a throwaway object\n\nWrite a small file with an explicit **governance-mode** retention of one day, read it\nback, then attempt to delete that object version. Under a working lock the delete must\nfail. If it succeeds, the destination is not immutable, whatever the configuration\nclaims.\n\n```bash\naws s3api put-object --bucket \"$BUCKET\" --key \"_lock-test\u002F$STAMP\" --body \"$TEST_FILE\" \\\n  --object-lock-mode GOVERNANCE --object-lock-retain-until-date \"$TOMORROW\"\naws s3api delete-object --bucket \"$BUCKET\" --key \"_lock-test\u002F$STAMP\" --version-id \"$VERSION_ID\"\n```\n\nNever test with compliance mode or a long retention: a compliance-mode test object\ncannot be deleted by anyone until it expires, and it is billed until then. The governance\ntest object expires after a day; deleting it sooner needs\n`--bypass-governance-retention` and the matching permission. An explicit retention on\nthe object overrides the bucket's default, so this tests the lock mechanism without\nleaving an undeletable object.\n\n### 5. Record the policy\n\nWrite the destination, protection model, retention period, and the date of this test\ninto `evidence\u002FPOLICY.md` under `STORAGE_REMOTE`. Record the test result, not the\nintention.\n\n## Output\n\n- A configured remote and a recorded destination policy.\n- The result of an actual immutability test.\n\n## Notes\n\n- A retention lock protects against deletion, not against a bad object being written in\n  the first place. Verify before syncing, not after.\n- Retention periods cost money for their whole duration. State that before a long\n  period is set.\n- One copy in one region is not a backup. Prefer two destinations with different\n  failure modes.\n","# Set Up Storage\n\nDefine where verified evidence is replicated, and confirm that the destination actually\nresists rewriting before anything is trusted to it.\n\n## When to use\n\n- During onboarding, once the local pipeline works.\n- Adding a second, independent destination.\n- Auditing whether an existing destination really is immutable.\n\n## Procedure\n\n### 1. Choose the protection model\n\nAsk which of these applies, because they fail differently:\n\n- **Object storage with a retention lock** — S3 Object Lock or an equivalent. Objects\n  cannot be deleted or overwritten until their retention expires. Requires versioning\n  on the bucket. Since November 2023 S3 can enable Object Lock on an existing bucket, so\n  a new bucket is not required; objects already in it are not locked until a retention\n  is set on each.\n- **Append-only or immutable-tier storage** — provider-enforced, no client cooperation\n  needed.\n- **Physical write-once media** — an optical disc or a WORM cartridge. Immutable by\n  construction, offline by default, and slow to recover from.\n- **An ordinary remote** — no protection at all. Usable as a second copy, but must not\n  be described as immutable.\n\nBe direct if the chosen destination provides no protection. An ordinary bucket with\ncareful habits is not immutable storage.\n\n### 2. Define the remote\n\nCreate the remote non-interactively, with credentials taken from the environment or the\nAWS credential chain rather than stored in the remote:\n\n```bash\nrclone config create \"$REMOTE\" s3 provider=AWS env_auth=true region=\"$REGION\" --non-interactive\nrclone listremotes\n```\n\nDo not run bare `rclone config`: it is an interactive wizard that prompts for access\nkeys. Never ask for a secret in conversation, never echo one, and never write one into\nthe workspace. If no credentials are available in the environment, stop and tell the\nuser to set them up themselves (for example `aws configure` in their own terminal).\n\n### 3. Confirm the bucket's actual settings\n\n```bash\naws s3api get-bucket-versioning --bucket \"$BUCKET\"\naws s3api get-object-lock-configuration --bucket \"$BUCKET\"\n```\n\nReport what these return rather than what was intended. An empty or missing\nObject Lock configuration means no lock, whatever the bucket was meant to have. Object\nLock can be enabled on an existing bucket (versioning must be on first), but that is a\nchange to the user's storage: state it and get agreement before running\n`put-object-lock-configuration`. Check, do not assume.\n\nNote which retention mode is configured. Governance mode can be bypassed by a\nsufficiently privileged user; compliance mode cannot be bypassed by anyone, including\nthe account root, until retention expires. That difference is the whole point, and it\nis also irreversible — say so before anyone chooses compliance mode.\n\n### 4. Test with a throwaway object\n\nWrite a small file with an explicit **governance-mode** retention of one day, read it\nback, then attempt to delete that object version. Under a working lock the delete must\nfail. If it succeeds, the destination is not immutable, whatever the configuration\nclaims.\n\n```bash\naws s3api put-object --bucket \"$BUCKET\" --key \"_lock-test\u002F$STAMP\" --body \"$TEST_FILE\" \\\n  --object-lock-mode GOVERNANCE --object-lock-retain-until-date \"$TOMORROW\"\naws s3api delete-object --bucket \"$BUCKET\" --key \"_lock-test\u002F$STAMP\" --version-id \"$VERSION_ID\"\n```\n\nNever test with compliance mode or a long retention: a compliance-mode test object\ncannot be deleted by anyone until it expires, and it is billed until then. The governance\ntest object expires after a day; deleting it sooner needs\n`--bypass-governance-retention` and the matching permission. An explicit retention on\nthe object overrides the bucket's default, so this tests the lock mechanism without\nleaving an undeletable object.\n\n### 5. Record the policy\n\nWrite the destination, protection model, retention period, and the date of this test\ninto `evidence\u002FPOLICY.md` under `STORAGE_REMOTE`. Record the test result, not the\nintention.\n\n## Output\n\n- A configured remote and a recorded destination policy.\n- The result of an actual immutability test.\n\n## Notes\n\n- A retention lock protects against deletion, not against a bad object being written in\n  the first place. Verify before syncing, not after.\n- Retention periods cost money for their whole duration. State that before a long\n  period is set.\n- One copy in one region is not a backup. Prefer two destinations with different\n  failure modes.\n",{"name":5,"description":7,"allowed-tools":24},"Bash(rclone *), Bash(aws *), Bash(command *), Bash(mkdir *), Read, Write","main","f846d9a97082ff30d613b55a085cef425d822473","plugins\u002Fevidence-ops\u002Fskills\u002Fsetup-storage","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle","https:\u002F\u002Fshotcowboystyle.github.io","Building smarter with AI, automation & modern tools. Exploring how far one person can go without a big team using today’s AI.","2026-11-10 04:58:27",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add shotcowboystyle\u002Fag-skills --skill setup-storage",{"tool":39,"command":40},"bunx","bunx skills add shotcowboystyle\u002Fag-skills --skill setup-storage",{"tool":42,"command":43},"pnpm","pnpm dlx skills add shotcowboystyle\u002Fag-skills --skill setup-storage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fevidence-ops\u002Fskills\u002Fsetup-storage\u002FSKILL.md",true,[],[48,54,61,68,75,82],{"skillNo":49,"name":50,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7F1YRY5S5QRJ1V0BJS130QX","no-description","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fno-description\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7F1Y9BV2FJNQJ3NB32JS5CM","good-skill","Fixture skill that satisfies every rule.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fgood-skill\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7F1XXBQ3NQRXZSS0KAGAR9V","broken-link","Links to a reference file that does not exist.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbroken-link\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7F1XBX4R46NR9W0HXQ7XCDX","Bad_Name","Name violates the kebab-case rule and does not match the directory.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbad-name\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7F1WNAF8WNEQ7S5HKT5VK0D","skill-authoring","Write, review, and validate portable agent skills in SKILL.md format. Use when creating a new skill, editing an existing one, or asked whether a skill follows the Agent Skills spec.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fskills\u002Fskill-authoring\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7F1W30TC0XFNSF7YBRGETK2","weigh-bags","Record scale readings for each bag — empty (tare), outbound, current, final — and reconcile them against the itemised inventory to find unaccounted weight. Use when the user gives a bag weight, says how heavy something is, weighs their luggage, or asks how close to the limit they are. Appends to bags.yaml and runs scripts\u002Freconcile.py.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Ftravel-packing-assistant\u002Fskills\u002Fweigh-bags\u002FSKILL.md",[],[]]