[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71NGF7M0K2162Q2G0DPXEEH":3,"skill-same:01M71NGF7M0K2162Q2G0DPXEEH":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":55,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":6,"updatedAt":63,"install":64,"resources":77},"01M71NGF7M0K2162Q2G0DPXEEH","payment-agent",null,"Use when an org role acts as payment agent and must execute charges, refunds or subscription changes for a user with least privilege and a full audit trail. Covers idempotency keys, confirming irreversible actions, never persisting cardholder data, and relying on native PCI-compliant platforms like Stripe.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fpayment-agent\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"payment","payment agent","refunds","context","full","org","security","stripe","data","subscription","audit","native","monomind","pci","audit trail","query","when","impact","actions","never","2026-11-10 10:56:23",false,"---\nname: payment-agent\ndescription: \"Use when an org role acts as payment agent and must execute charges, refunds or subscription changes for a user with least privilege and a full audit trail. Covers idempotency keys, confirming irreversible actions, never persisting cardholder data, and relying on native PCI-compliant platforms like Stripe.\"\ntags: [\"engineering\",\"security\",\"stripe\",\"compliance\"]\ntools: [\"monograph_query\",\"monograph_context\",\"monograph_impact\"]\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\n---\n# Payment Agent — Best Practices\n\n## Focus\nExecutes payment and billing operations on a user's behalf (charges, refunds, subscription changes) with strict least-privilege access, auditability, and zero tolerance for wrong or unauthorized actions.\n\n## Best practices\n- Operate under least-privilege scopes — request only the specific payment actions needed for the task, never broad account access.\n- Use idempotency keys on every mutating payment call so retries or network failures can't cause duplicate charges or refunds.\n- Never persist raw cardholder data (card numbers, CVV) even transiently in logs, memory dumps, or intermediate storage — redact before it touches any store.\n- Confirm the exact action (amount, recipient, subscription tier) with the user before executing anything irreversible — a correct-sounding but wrong mutation is worse than doing nothing.\n- Rely on native, PCI-compliant payment platform integrations (Stripe, etc.) rather than building custom cardholder-data handling.\n- Log every payment action with actor, amount, timestamp, and outcome for auditability — payments need a complete trail, not just success\u002Ffailure.\n- Validate outputs against real account state before acting — don't trust a cached or inferred balance for a decision that moves money.\n\n## Common pitfalls\n- Treating \"answered the billing question correctly\" as equivalent to \"took the correct action\" — an agent that explains billing well but executes the wrong Stripe mutation is worse than one that does nothing.\n- Missing idempotency handling, causing duplicate charges\u002Frefunds on retry.\n- Over-privileged agent credentials that can perform actions well beyond what any single task requires.\n- Storing or transmitting cardholder data outside of TLS 1.2+, or logging it in plaintext during debugging.\n\n## Tools & techniques\n- Idempotency keys on all state-changing payment API calls.\n- Native payment-platform integrations that handle webhook reconciliation and idempotency out of the box, instead of hand-rolled reconciliation logic.\n- Explicit confirmation step before any irreversible financial action (charge, refund, cancellation) — never auto-execute on inference alone.\n- Access audit trail per agent identity: what it's allowed to do, and a log of what it actually did.\n- MFA \u002F strong authentication on any credential the agent uses to reach payment infrastructure.\n","# Payment Agent — Best Practices\n\n## Focus\nExecutes payment and billing operations on a user's behalf (charges, refunds, subscription changes) with strict least-privilege access, auditability, and zero tolerance for wrong or unauthorized actions.\n\n## Best practices\n- Operate under least-privilege scopes — request only the specific payment actions needed for the task, never broad account access.\n- Use idempotency keys on every mutating payment call so retries or network failures can't cause duplicate charges or refunds.\n- Never persist raw cardholder data (card numbers, CVV) even transiently in logs, memory dumps, or intermediate storage — redact before it touches any store.\n- Confirm the exact action (amount, recipient, subscription tier) with the user before executing anything irreversible — a correct-sounding but wrong mutation is worse than doing nothing.\n- Rely on native, PCI-compliant payment platform integrations (Stripe, etc.) rather than building custom cardholder-data handling.\n- Log every payment action with actor, amount, timestamp, and outcome for auditability — payments need a complete trail, not just success\u002Ffailure.\n- Validate outputs against real account state before acting — don't trust a cached or inferred balance for a decision that moves money.\n\n## Common pitfalls\n- Treating \"answered the billing question correctly\" as equivalent to \"took the correct action\" — an agent that explains billing well but executes the wrong Stripe mutation is worse than one that does nothing.\n- Missing idempotency handling, causing duplicate charges\u002Frefunds on retry.\n- Over-privileged agent credentials that can perform actions well beyond what any single task requires.\n- Storing or transmitting cardholder data outside of TLS 1.2+, or logging it in plaintext during debugging.\n\n## Tools & techniques\n- Idempotency keys on all state-changing payment API calls.\n- Native payment-platform integrations that handle webhook reconciliation and idempotency out of the box, instead of hand-rolled reconciliation logic.\n- Explicit confirmation step before any irreversible financial action (charge, refund, cancellation) — never auto-execute on inference alone.\n- Access audit trail per agent identity: what it's allowed to do, and a log of what it actually did.\n- MFA \u002F strong authentication on any credential the agent uses to reach payment infrastructure.\n",{"name":5,"tags":48,"tools":51,"source":55,"license":14,"description":7},[49,29,30,50],"engineering","compliance",[52,53,54],"monograph_query","monograph_context","monograph_impact","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fpayment-agent",2,"https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-14 03:30:52",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add monoes\u002Fmonomind --skill payment-agent",{"tool":70,"command":71},"bunx","bunx skills add monoes\u002Fmonomind --skill payment-agent",{"tool":73,"command":74},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill payment-agent","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fpayment-agent\u002FSKILL.md",true,[],[79,102,135,162,186,210],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":101},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[86,87,88,89,90,91,92,93,40,38,94,95,35,96,97,98,99,29,28,100],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","knowledge","snark","review","security review","stark","zettelkasten","cryptography","blockchain","2026-11-10 13:02:02",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":106,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":118,"publishedAt":101},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[110,113],{"categoryNo":111,"categoryName":112,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":114,"categoryName":115,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[119,120,121,90,122,123,39,124,38,125,126,127,128,129,130,131,132,133,26,134],"writing","writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","product","write","commands","paths","suggest","coding","ZeRO",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":139,"sourceHtmlUrl":140,"categories":141,"keywords":145,"publishedAt":101},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[142],{"categoryNo":143,"categoryName":144,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000031","产品经理",[129,146,147,148,149,93,150,39,151,152,153,128,154,155,156,157,158,159,160,161],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","use","document",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":166,"sourceHtmlUrl":167,"categories":168,"keywords":172,"publishedAt":101},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[169],{"categoryNo":170,"categoryName":171,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000033","数据分析师",[38,129,173,174,175,176,93,160,39,177,178,179,180,153,181,182,183,184,185,31],"write query","postgres","for","snowflake","best practices","natural-language","with","multi","github","sql","https","syntax","plugins",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":196,"publishedAt":101},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[192,195],{"categoryNo":193,"categoryName":194,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[197,198,199,200,175,41,201,202,203,40,204,205,206,38,35,181,207,208,209,183],"Workflow Automation","automation","workflow","parallel","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":214,"categories":215,"keywords":217,"publishedAt":101},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[216],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[199,218,219,220,221,222,223,175,224,225,125,226,227,228,35,181,229,230,183,231],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]