[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C494CV5NS1GN327C48M2XE":3,"skill-same:01M6C494CV5NS1GN327C48M2XE":76},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":54,"commitSha":55,"skillDirectory":5,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M6C494CV5NS1GN327C48M2XE","how-to-write-rulebooks",null,"A practical, step-by-step guide that standardizes how to author, structure and publish rulebooks in Stakpak. It covers metadata creation, goal articulation, workflow design, reference inclusion and best-practice guidelines.","stakpak\u002Fcommunity-paks","stakpak","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F86326525?v=4","01M6C48005ADA10YG0BQQX0J4Q","Stakpak","01M6C4804JD6KKZR9AQ9TYS0BT",4,"MIT","https:\u002F\u002Fgithub.com\u002Fstakpak\u002Fcommunity-paks\u002Fblob\u002Fmain\u002Fhow-to-write-rulebooks\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"write","how to write rulebooks","how","management","cli","stakpak-cli","best-practice","devops-automation","rulebook-creation","goal","devops","knowledge-management","automation","design","knowledge","workflow","team","publish","dev","guidelines","2026-11-10 10:12:30",false,"---\nname: how-to-write-rulebooks\ndescription: |\n  A practical, step-by-step guide that standardizes how to author, structure and publish rulebooks in Stakpak. It covers metadata creation, goal articulation, workflow design, reference inclusion and best-practice guidelines.\nlicense: MIT\ntags:\n  - rulebook-creation\n  - knowledge-management\n  - devops-automation\n  - best-practice\n  - stakpak-cli\nmetadata:\n  author: Stakpak \u003Cteam@stakpak.dev>\n  version: \"1.0.2\"\n---\n\n## Goals\n\n* Make it easy for anyone to write and share Rulebooks\n\n* Standardize how operational knowledge is captured and reused\n\n* Enable Stakpak to help users create high quality Rulebooks\n\n## Workflow\n\nWhen generating a new Rule Book, always follow this process:\n\n### Step 1: Start with Metadata\n\n**URI:** \u003Ccategory>\u002F\u003Cname>\\\n**Description:** The description will help Stakpak know what this Rulebook is about, its scope, and when to use it, keep this short and to the point\\\n**Tags:** create at least three tags to help Stakpak find this Rulebook in the future with keyword search\n\n### Step 2: Write the Goals\n\nExplain the outcome the user will achieve by following this Rule Book. The goal should be written as a clear, outcome oriented sentence:\n\n**Bad:** \"This Rule Book is about Kubernetes.\"\n\n**Good:** \"This Rule Book helps you deploy and scale applications on Kubernetes with production grade configuration.\"\n\n### Step 3: Write the Workflow\n\nProvide a numbered, step by step guide that explains how to accomplish the goal, maximize re-usability by avoiding hard coded values.\n\nEach step should include:\n\n**Action:** Imperative instruction (e.g., \"Install the CLI tool\").\n\n**Reasoning:** Why this step is required (optional but recommended).\n\n**Examples:** Code samples, commands, or configuration snippets where applicable.\n\nGuidelines:\n\n* Use short, direct sentences\n\n* Keep steps atomic (one action per step)\n\n* Include necessary context but avoid unnecessary details and hard-coded literals\n\n### Step 4: Add References\n\nConclude the Rule Book with a \"References\" section.\\\nThis section should contain:\n\n* Links to official documentation or standards\n\n* Related Rulebooks\n\n* External resources for deeper learning\n\n### Best Practices for Writing a Rule Book\n\n* Use a clear structure, and concise text\n\n* Only include new information and insights learned throughout the session, for example good patterns you see, and information you learn by doing web research. This information should complement LLM agents, so repeating knowledge the agent already processes is redundant and reduces the quality of this Rulebook\n\n* You can add a prerequisites with conditions and initial requirements in the description (e.g. only run if there is Terraform code)\n\n* You can ask the agent in the Rulebook to follow certain standards and guidelines\n\n  * Principle of least privilege\n\n  * OWASP Guidelines (with reference to which guidelines exactly)\n\n  * AWS Well Architected Framework\n\n  * Or even your internal company guidelines found in other Rulebooks (with reference)\n\n### Using the stakpak CLI to manage Rulebook\n\n```\n# Get rulebook(s) (URI is optional - if not provided, lists all rulebooks)\nstakpak rb get [URI]\n\n# Apply\u002Fcreate a rulebook from a markdown file\nstakpak rb apply \u003CFILE_PATH>\n\n# Delete a rulebook\nstakpak rb delete \u003CURI>\n```\n","## Goals\n\n* Make it easy for anyone to write and share Rulebooks\n\n* Standardize how operational knowledge is captured and reused\n\n* Enable Stakpak to help users create high quality Rulebooks\n\n## Workflow\n\nWhen generating a new Rule Book, always follow this process:\n\n### Step 1: Start with Metadata\n\n**URI:** \u003Ccategory>\u002F\u003Cname>\\\n**Description:** The description will help Stakpak know what this Rulebook is about, its scope, and when to use it, keep this short and to the point\\\n**Tags:** create at least three tags to help Stakpak find this Rulebook in the future with keyword search\n\n### Step 2: Write the Goals\n\nExplain the outcome the user will achieve by following this Rule Book. The goal should be written as a clear, outcome oriented sentence:\n\n**Bad:** \"This Rule Book is about Kubernetes.\"\n\n**Good:** \"This Rule Book helps you deploy and scale applications on Kubernetes with production grade configuration.\"\n\n### Step 3: Write the Workflow\n\nProvide a numbered, step by step guide that explains how to accomplish the goal, maximize re-usability by avoiding hard coded values.\n\nEach step should include:\n\n**Action:** Imperative instruction (e.g., \"Install the CLI tool\").\n\n**Reasoning:** Why this step is required (optional but recommended).\n\n**Examples:** Code samples, commands, or configuration snippets where applicable.\n\nGuidelines:\n\n* Use short, direct sentences\n\n* Keep steps atomic (one action per step)\n\n* Include necessary context but avoid unnecessary details and hard-coded literals\n\n### Step 4: Add References\n\nConclude the Rule Book with a \"References\" section.\\\nThis section should contain:\n\n* Links to official documentation or standards\n\n* Related Rulebooks\n\n* External resources for deeper learning\n\n### Best Practices for Writing a Rule Book\n\n* Use a clear structure, and concise text\n\n* Only include new information and insights learned throughout the session, for example good patterns you see, and information you learn by doing web research. This information should complement LLM agents, so repeating knowledge the agent already processes is redundant and reduces the quality of this Rulebook\n\n* You can add a prerequisites with conditions and initial requirements in the description (e.g. only run if there is Terraform code)\n\n* You can ask the agent in the Rulebook to follow certain standards and guidelines\n\n  * Principle of least privilege\n\n  * OWASP Guidelines (with reference to which guidelines exactly)\n\n  * AWS Well Architected Framework\n\n  * Or even your internal company guidelines found in other Rulebooks (with reference)\n\n### Using the stakpak CLI to manage Rulebook\n\n```\n# Get rulebook(s) (URI is optional - if not provided, lists all rulebooks)\nstakpak rb get [URI]\n\n# Apply\u002Fcreate a rulebook from a markdown file\nstakpak rb apply \u003CFILE_PATH>\n\n# Delete a rulebook\nstakpak rb delete \u003CURI>\n```\n",{"name":5,"tags":49,"license":15,"metadata":50,"description":53},[32,35,31,30,29],{"author":51,"version":52},"Stakpak \u003Cteam@stakpak.dev>","1.0.2","A practical, step-by-step guide that standardizes how to author, structure and publish rulebooks in Stakpak. It covers metadata creation, goal articulation, workflow design, reference inclusion and best-practice guidelines.\n","main","d9bbde9885439c55adad930456b2660b0c37c052",1,"https:\u002F\u002Fgithub.com\u002Fstakpak\u002Fcommunity-paks","https:\u002F\u002Fgithub.com\u002Fstakpak","https:\u002F\u002Fwww.stakpak.dev","AI that runs your Infra","2026-07-04 20:18:32",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add stakpak\u002Fcommunity-paks --skill how-to-write-rulebooks",{"tool":68,"command":69},"bunx","bunx skills add stakpak\u002Fcommunity-paks --skill how-to-write-rulebooks",{"tool":71,"command":72},"pnpm","pnpm dlx skills add stakpak\u002Fcommunity-paks --skill how-to-write-rulebooks","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstakpak\u002Fcommunity-paks\u002Fblob\u002Fmain\u002Fhow-to-write-rulebooks\u002FSKILL.md",true,[],[77,112,136,153,173,191],{"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":94,"publishedAt":44},"01M6C49TTAVC8Q9CTTC05F6VSR","vllm-deployment","Deploy vLLM for high-performance LLM inference. Covers Docker CPU\u002FGPU deployments and cloud VM provisioning with OpenAI-compatible API endpoints.","https:\u002F\u002Fgithub.com\u002Fstakpak\u002Fcommunity-paks\u002Fblob\u002Fmain\u002Fvllm-deployment\u002FSKILL.md",[83,86,89],{"categoryNo":84,"categoryName":85,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":87,"categoryName":88,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[95,96,97,98,99,100,101,102,40,103,104,105,106,107,42,108,109,110,111],"vllm deployment","vLLM","deployment","docker","cloud","openai-api","llm inference","learning","api","provisioning","machine-learning","gpu","openai","vm","deploy","performance","inference",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":119,"publishedAt":44},"01M6C49R31XN7KJ7Y0Y78XVYTQ","terrateam-usage-guide","A comprehensive guide for configuring and using Terrateam, an open-source GitOps CI\u002FCD platform for Terraform and OpenTofu. Covers configuration file structure, access control, workflows, OIDC authentication, drift detection, and best practices for managing infrastructure through pull requests.","https:\u002F\u002Fgithub.com\u002Fstakpak\u002Fcommunity-paks\u002Fblob\u002Fmain\u002Fterrateam-usage-guide\u002FSKILL.md",[118],{"categoryNo":87,"categoryName":88,"taxonomyType":21,"taxonomyTypeDesc":22},[120,121,122,123,124,40,125,126,127,128,129,42,130,131,132,133,134,135],"terrateam usage guide","guide","file","opentofu","access","open","detection","oidc","ci","pull","terraform","best practices","authentication","infrastructure","pull requests","workflows",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":44},"01M6C49N78AMM570EGPDXEZZDY","simple-deployment-on-vm","How to do simple but secure deployments using virtual machines on different cloud providers","https:\u002F\u002Fgithub.com\u002Fstakpak\u002Fcommunity-paks\u002Fblob\u002Fmain\u002Fsimple-deployment-on-vm\u002FSKILL.md",[],[143,108,97,144,42,145,26,40,146,147,148,149,150,99,151,109,152],"simple deployment on vm","tls configuration","virtual","ec2","Providers","tls","aws","dns","secure","security",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":44},"01M6C49J8PRVT623JWRTTKFNJV","nextjs-on-aws","This document compares various AWS deployment options for Next.js applications, analyzing costs, benefits, limitations, and providing recommendations based on different use cases.","https:\u002F\u002Fgithub.com\u002Fstakpak\u002Fcommunity-paks\u002Fblob\u002Fmain\u002Fnextjs-on-aws\u002FSKILL.md",[],[160,149,161,162,163,164,40,165,166,167,168,169,42,97,170,171,172],"nextjs on aws","nextjs","use","aws deployment","js","Next.js","analysis","applications","analyzing","cost","architecture","migration","cost-analysis",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":179,"publishedAt":44},"01M6C49F5B4BF2CHNT4X08XP69","migrating-bitnami-to-bitnami-legacy","This rule book helps you migrate Bitnami Helm charts and container images from the bitnami repository to the bitnamilegacy repository.\n\nThis migration is necessary due to Bitnami's transition, effective August 28th, 2025, where existing images will be moved to the legacy repo","https:\u002F\u002Fgithub.com\u002Fstakpak\u002Fcommunity-paks\u002Fblob\u002Fmain\u002Fmigrating-bitnami-to-bitnami-legacy\u002FSKILL.md",[],[180,181,40,182,183,184,185,186,187,188,42,189,190],"migrating bitnami to bitnami legacy","container images","helm","migrate","bitnami-helm-charts","bitnami-legacy","bitnami","container","repo","repository","Charts",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":197,"publishedAt":44},"01M6C49CHCPGZZ42P5W1MTV3WS","k3s-backup","Backup and recovery solution for K3s clusters. Includes scheduled, pre-shutdown, and manual backup strategies with recovery procedures.","https:\u002F\u002Fgithub.com\u002Fstakpak\u002Fcommunity-paks\u002Fblob\u002Fmain\u002Fk3s-backup\u002FSKILL.md",[],[198,199,200,42,201,40],"backup","k3s","k3s backup","recovery"]