[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EN65JF34GKPY0FVG6SETMT":3,"skill-same:01M7EN65JF34GKPY0FVG6SETMT":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":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EN65JF34GKPY0FVG6SETMT","gpg-expert",null,"GPG guidance — key management, signing commits, encrypting files, subkeys, revocation, and YubiKey workflows.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-gpg-expert\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: gpg-expert\ndescription: GPG guidance — key management, signing commits, encrypting files, subkeys, revocation, and YubiKey workflows.\ncategory: development\n---\n\n## Overview\n\nGPG (GNU Privacy Guard) is the OpenPGP implementation behind signed git commits, encrypted files, and verified software releases. Its reputation for being hard to use is deserved — but the working subset (generate a key, sign commits, encrypt to recipients, manage subkeys, revoke when needed) is learnable in an afternoon and covers 95% of real usage.\n\nThis skill covers that working subset plus the operational practices that matter: subkeys for daily use, hardware keys (YubiKey) for high-value identities, revocation certificates generated before you need them, and the keyserver\u002FWeb-of-Trust realities of 2026.\n\n## When to use\n\n- Signing git commits and tags.\n- Encrypting files or secrets for specific recipients.\n- Setting up GPG subkeys and moving keys to a YubiKey.\n- Generating revocation certificates.\n- Verifying signatures on releases.\n- Choosing between GPG, age, and SSH-based signing.\n\n## Core concepts\n\n- **Key pairs.** A primary key (certify + optionally sign) and subkeys (sign, encrypt, authenticate). The primary key is your identity — protect it; subkeys do daily work and are replaceable.\n- **Subkeys.** Separate sign\u002Fencrypt\u002Fauth subkeys under one primary. Laptop compromise? Revoke the subkeys, keep the identity. This separation is the single most important GPG practice.\n- **Web of Trust vs TOFU.** The WoT (keysigning parties) never scaled; in practice, trust is TOFU (trust on first use) plus verification through another channel (a video call, a known website, Keybase-style proofs). Set ownertrust realistically.\n- **Keyservers.** SKS is dead (poisoned keys, GDPR issues); modern keys.openpgp.org is the sane default — it verifies email ownership before publishing. Don't upload keys you can't maintain.\n- **Signing vs encrypting.** Sign = authenticity\u002Fintegrity (anyone can verify, message readable). Encrypt = confidentiality (only recipients read). Sign-then-encrypt for both. Git commits use signing.\n- **Detached signatures.** `.sig`\u002F`.asc` files alongside releases — `gpg --verify` checks authenticity without hiding the content. The standard for software distribution.\n- **Revocation certificates.** Generate at key creation (`gpg --gen-revoke`, stored offline) — revoking a lost\u002Fcompromised key without the private key is impossible otherwise. This is the \"backup\" most people skip.\n- **YubiKey \u002F hardware keys.** Private key material generated on (or moved to) the token; signing\u002Fdecryption require touch. The primary key lives offline; subkeys live on the YubiKey. `gpg --card-status` inspects.\n- **gpg-agent.** Caches passphrases, integrates with pinentry; `gpg-agent` also provides SSH auth via the auth subkey (`enable-ssh-support`) — one hardware token for GPG + SSH.\n- **Trust model for verification.** `gpg --verify` tells you the signature is valid AND whether you trust the key — \"Good signature\" from an untrusted key is informational, not assurance. Distinguish the two outputs.\n- **Expiry.** Keys and subkeys should expire (1-2 years) — expiry is self-updating (extend anytime you hold the key) and bounds the damage of a lost key. Non-expiring keys are a liability.\n- **age as the alternative.** For pure file encryption, `age` is simpler and modern (no keyrings, no WoT). Use GPG where signatures\u002Fidentity matter; age where you just need \"encrypt this file to this recipient.\"\n- **SSH signing for git.** Git can sign with SSH keys (`gpg.format ssh`) — simpler if you already manage SSH keys, and GitHub verifies them. GPG remains the choice for encryption and the broader OpenPGP ecosystem.\n- **Key rotation statements.** When rotating keys, publish a statement signed by the old key linking old and new fingerprints — prevents impersonation confusion during the transition.\n\n## Practical workflow\n\n1. **Generate properly.** Primary cert-only key + sign\u002Fencrypt\u002Fauth subkeys, with expirations, and a revocation cert stored offline:\n   ```bash\n   gpg --quick-generate-key \"Ada Lovelace \u003Cada@example.com>\" ed25519 cert 2y\n   gpg --quick-add-key \u003Cfingerprint> ed25519 sign 1y\n   gpg --quick-add-key \u003Cfingerprint> cv25519 encrypt 1y\n   gpg --output revoke.asc --gen-revoke \u003Cfingerprint>  # store OFFLINE\n   ```\n2. **Back up.** Export the full key (primary + subkeys) to encrypted offline media; export the public key for publishing. Test restore on a scratch machine — backups you can't restore are theater.\n3. **Move subkeys to YubiKey.** `keytocard` for each subkey; verify with `gpg --card-status`; delete the on-disk secret subkeys after confirming (`gpg --delete-secret-subkeys`, keeping the primary offline).\n4. **Sign git commits.** Configure git once; sign by default:\n   ```bash\n   git config --global user.signingkey \u003Csigning-subkey-id>\n   git config --global commit.gpgsign true\n   git config --global tag.gpgsign true\n   # or SSH signing: git config --global gpg.format ssh\n   ```\n5. **Encrypt files to recipients.** `--encrypt --recipient` (can list several); `--armor` for text-safe output:\n   ```bash\n   gpg --encrypt --recipient ada@example.com --armor secrets.env\n   gpg --decrypt secrets.env.asc\n   ```\n6. **Verify releases.** Import the project's key from a trustworthy source, check the fingerprint out-of-band, then `gpg --verify file.sig file`. Read both the validity AND trust lines.\n7. **Publish thoughtfully.** `gpg --send-keys` to keys.openpgp.org (verifies your email); keep a public key page with the fingerprint for out-of-band verification.\n8. **Rotate and revoke.** Extend expirations yearly; if a subkey is compromised, revoke just the subkey and roll a new one — the identity (primary) survives.\n\n## Common pitfalls\n\n- **No revocation certificate** — lost key = unrevocable identity; generate at creation, store offline.\n- **Daily-driving the primary key** — compromise costs the identity; subkeys for daily use, primary offline.\n- **Non-expiring keys** — unbounded liability; 1-2 year expirations, extendable anytime.\n- **Uploading to dead keyservers** — SKS poisoning\u002FGDPR; use keys.openpgp.org.\n- **Confusing \"Good signature\" with trust** — validity ≠ trust; check the trust line.\n- **Passphraseless keys** — a copied `~\u002F.gnupg` is full impersonation; passphrases + agent.\n- **Forgetting `gpg-agent`** — typing passphrases constantly; agent + pinentry configured once.\n- **Encrypting without signing** — recipient can't verify sender; sign-then-encrypt for authenticity.\n- **Wrong recipient \u002F no self-encryption** — encrypting to others without including yourself; add yourself as recipient or you can't read your own files.\n- **YubiKey without backup** — token lost = subkeys lost; keep offline subkey backups for re-provisioning.\n- **Fingerprint not verified out-of-band** — trusting a keyserver alone; verify fingerprints via a second channel.\n- **GPG for what age does better** — keyring ceremony for simple file encryption; age for encryption-only needs.\n- **Expired subkeys breaking CI** — signing keys expiring unnoticed; monitor expirations and rotate proactively.\n","## Overview\n\nGPG (GNU Privacy Guard) is the OpenPGP implementation behind signed git commits, encrypted files, and verified software releases. Its reputation for being hard to use is deserved — but the working subset (generate a key, sign commits, encrypt to recipients, manage subkeys, revoke when needed) is learnable in an afternoon and covers 95% of real usage.\n\nThis skill covers that working subset plus the operational practices that matter: subkeys for daily use, hardware keys (YubiKey) for high-value identities, revocation certificates generated before you need them, and the keyserver\u002FWeb-of-Trust realities of 2026.\n\n## When to use\n\n- Signing git commits and tags.\n- Encrypting files or secrets for specific recipients.\n- Setting up GPG subkeys and moving keys to a YubiKey.\n- Generating revocation certificates.\n- Verifying signatures on releases.\n- Choosing between GPG, age, and SSH-based signing.\n\n## Core concepts\n\n- **Key pairs.** A primary key (certify + optionally sign) and subkeys (sign, encrypt, authenticate). The primary key is your identity — protect it; subkeys do daily work and are replaceable.\n- **Subkeys.** Separate sign\u002Fencrypt\u002Fauth subkeys under one primary. Laptop compromise? Revoke the subkeys, keep the identity. This separation is the single most important GPG practice.\n- **Web of Trust vs TOFU.** The WoT (keysigning parties) never scaled; in practice, trust is TOFU (trust on first use) plus verification through another channel (a video call, a known website, Keybase-style proofs). Set ownertrust realistically.\n- **Keyservers.** SKS is dead (poisoned keys, GDPR issues); modern keys.openpgp.org is the sane default — it verifies email ownership before publishing. Don't upload keys you can't maintain.\n- **Signing vs encrypting.** Sign = authenticity\u002Fintegrity (anyone can verify, message readable). Encrypt = confidentiality (only recipients read). Sign-then-encrypt for both. Git commits use signing.\n- **Detached signatures.** `.sig`\u002F`.asc` files alongside releases — `gpg --verify` checks authenticity without hiding the content. The standard for software distribution.\n- **Revocation certificates.** Generate at key creation (`gpg --gen-revoke`, stored offline) — revoking a lost\u002Fcompromised key without the private key is impossible otherwise. This is the \"backup\" most people skip.\n- **YubiKey \u002F hardware keys.** Private key material generated on (or moved to) the token; signing\u002Fdecryption require touch. The primary key lives offline; subkeys live on the YubiKey. `gpg --card-status` inspects.\n- **gpg-agent.** Caches passphrases, integrates with pinentry; `gpg-agent` also provides SSH auth via the auth subkey (`enable-ssh-support`) — one hardware token for GPG + SSH.\n- **Trust model for verification.** `gpg --verify` tells you the signature is valid AND whether you trust the key — \"Good signature\" from an untrusted key is informational, not assurance. Distinguish the two outputs.\n- **Expiry.** Keys and subkeys should expire (1-2 years) — expiry is self-updating (extend anytime you hold the key) and bounds the damage of a lost key. Non-expiring keys are a liability.\n- **age as the alternative.** For pure file encryption, `age` is simpler and modern (no keyrings, no WoT). Use GPG where signatures\u002Fidentity matter; age where you just need \"encrypt this file to this recipient.\"\n- **SSH signing for git.** Git can sign with SSH keys (`gpg.format ssh`) — simpler if you already manage SSH keys, and GitHub verifies them. GPG remains the choice for encryption and the broader OpenPGP ecosystem.\n- **Key rotation statements.** When rotating keys, publish a statement signed by the old key linking old and new fingerprints — prevents impersonation confusion during the transition.\n\n## Practical workflow\n\n1. **Generate properly.** Primary cert-only key + sign\u002Fencrypt\u002Fauth subkeys, with expirations, and a revocation cert stored offline:\n   ```bash\n   gpg --quick-generate-key \"Ada Lovelace \u003Cada@example.com>\" ed25519 cert 2y\n   gpg --quick-add-key \u003Cfingerprint> ed25519 sign 1y\n   gpg --quick-add-key \u003Cfingerprint> cv25519 encrypt 1y\n   gpg --output revoke.asc --gen-revoke \u003Cfingerprint>  # store OFFLINE\n   ```\n2. **Back up.** Export the full key (primary + subkeys) to encrypted offline media; export the public key for publishing. Test restore on a scratch machine — backups you can't restore are theater.\n3. **Move subkeys to YubiKey.** `keytocard` for each subkey; verify with `gpg --card-status`; delete the on-disk secret subkeys after confirming (`gpg --delete-secret-subkeys`, keeping the primary offline).\n4. **Sign git commits.** Configure git once; sign by default:\n   ```bash\n   git config --global user.signingkey \u003Csigning-subkey-id>\n   git config --global commit.gpgsign true\n   git config --global tag.gpgsign true\n   # or SSH signing: git config --global gpg.format ssh\n   ```\n5. **Encrypt files to recipients.** `--encrypt --recipient` (can list several); `--armor` for text-safe output:\n   ```bash\n   gpg --encrypt --recipient ada@example.com --armor secrets.env\n   gpg --decrypt secrets.env.asc\n   ```\n6. **Verify releases.** Import the project's key from a trustworthy source, check the fingerprint out-of-band, then `gpg --verify file.sig file`. Read both the validity AND trust lines.\n7. **Publish thoughtfully.** `gpg --send-keys` to keys.openpgp.org (verifies your email); keep a public key page with the fingerprint for out-of-band verification.\n8. **Rotate and revoke.** Extend expirations yearly; if a subkey is compromised, revoke just the subkey and roll a new one — the identity (primary) survives.\n\n## Common pitfalls\n\n- **No revocation certificate** — lost key = unrevocable identity; generate at creation, store offline.\n- **Daily-driving the primary key** — compromise costs the identity; subkeys for daily use, primary offline.\n- **Non-expiring keys** — unbounded liability; 1-2 year expirations, extendable anytime.\n- **Uploading to dead keyservers** — SKS poisoning\u002FGDPR; use keys.openpgp.org.\n- **Confusing \"Good signature\" with trust** — validity ≠ trust; check the trust line.\n- **Passphraseless keys** — a copied `~\u002F.gnupg` is full impersonation; passphrases + agent.\n- **Forgetting `gpg-agent`** — typing passphrases constantly; agent + pinentry configured once.\n- **Encrypting without signing** — recipient can't verify sender; sign-then-encrypt for authenticity.\n- **Wrong recipient \u002F no self-encryption** — encrypting to others without including yourself; add yourself as recipient or you can't read your own files.\n- **YubiKey without backup** — token lost = subkeys lost; keep offline subkey backups for re-provisioning.\n- **Fingerprint not verified out-of-band** — trusting a keyserver alone; verify fingerprints via a second channel.\n- **GPG for what age does better** — keyring ceremony for simple file encryption; age for encryption-only needs.\n- **Expired subkeys breaking CI** — signing keys expiring unnoticed; monitor expirations and rotate proactively.\n",{"name":5,"category":24,"description":7},"development","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-gpg-expert",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill gpg-expert",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill gpg-expert",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill gpg-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-gpg-expert\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]