[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CAWD0380E2WAYR8WFF5895":3,"skill-same:01M6CAWD0380E2WAYR8WFF5895":66},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":47,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M6CAWD0380E2WAYR8WFF5895","daemon-init",null,"Initialize AIWG daemon mode configuration from a named profile for persistent background sessions","jmagly\u002Faiwg","jmagly","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1159087?v=4","01M6C10AK8N2WCSQN11FYGTJWN","Joseph Magly","01M6C10AQ8A2RMED1Y1BSVY7NF",229,"MIT","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Futils\u002Fskills\u002Fdaemon-init\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33],"init","daemon init","daemon","sessions","initialize","profile","configuration","mode","for","background","2026-11-10 10:12:30",false,"---\nnamespace: aiwg\nname: daemon-init\nplatforms: [all]\ndescription: Initialize AIWG daemon mode configuration from a named profile for persistent background sessions\n\n---\n\n# Daemon Init\n\nYou initialize AIWG daemon mode configuration from a named profile. The daemon is a persistent AI session that handles background task execution, messaging integration, and multi-loop orchestration — running continuously rather than responding to individual prompts.\n\n## Triggers\n\nAlternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):\n\n- \"start daemon mode\" → init with default profile\n- \"set up background agent\" → init with manager profile\n- \"configure aiwg for continuous operation\" → init with orchestrator profile\n- \"i want aiwg running in the background\" → init with manager profile\n- \"reinitialize daemon\" → init with `--force`\n\n## Trigger Patterns Reference\n\n| Pattern | Example | Action |\n|---------|---------|--------|\n| Default init | \"initialize daemon\" | Run `aiwg daemon-init` |\n| Named profile | \"init daemon as orchestrator\" | Run `aiwg daemon-init orchestrator` |\n| Force reinit | \"reinitialize daemon config\" | Run `aiwg daemon-init --force` |\n| Worker mode | \"set up a worker daemon\" | Run `aiwg daemon-init worker` |\n| Monitor mode | \"run daemon in monitoring mode\" | Run `aiwg daemon-init monitor` |\n\n## Behavior\n\nWhen triggered:\n\n1. **Extract intent**:\n   - Is a profile name specified? Default to `manager` if not.\n   - Is `--force` needed (user mentioned reinitializing or overwriting)?\n\n2. **Select the appropriate profile**:\n\n   | Profile | Authority | Use Case |\n   |---------|-----------|----------|\n   | `manager` (default) | Balanced — orchestrate and execute | General-purpose persistent agent |\n   | `orchestrator` | High — coordinate other agents | Driving multi-agent workflows |\n   | `worker` | Low — execute, minimal decisions | Background task execution |\n   | `monitor` | Read-only — observe and alert | Ops monitoring, health checks |\n\n3. **Run the command**:\n\n   ```bash\n   # Default profile (manager)\n   aiwg daemon-init\n\n   # Named profile\n   aiwg daemon-init orchestrator\n   aiwg daemon-init worker\n   aiwg daemon-init monitor\n\n   # Overwrite existing config\n   aiwg daemon-init --force\n   aiwg daemon-init orchestrator --force\n   ```\n\n4. **Know where config is written**: `.aiwg\u002Fdaemon\u002Fconfig.yaml` in the current project. This file controls:\n   - Session persistence behavior\n   - Messaging integration endpoints (Telegram, Slack, etc.)\n   - Task queue and loop settings\n   - Authority level and decision boundaries\n\n5. **Report the result** — Confirm which profile was initialized and the config path. If daemon is already initialized, remind the user to use `--force` to overwrite.\n\n## Examples\n\n### Example 1: Default initialization\n\n**User**: \"Set up daemon mode\"\n\n**Extraction**: Init request, no profile specified — use `manager`\n\n**Action**:\n```bash\naiwg daemon-init\n```\n\n**Response**: \"Daemon initialized with `manager` profile. Config written to `.aiwg\u002Fdaemon\u002Fconfig.yaml`. To start the daemon, see `docs\u002Fdaemon-guide.md` for session launch instructions.\"\n\n---\n\n### Example 2: Orchestrator profile\n\n**User**: \"Initialize the daemon as an orchestrator — I want it coordinating multiple sub-agents\"\n\n**Extraction**: Init with `orchestrator` profile\n\n**Action**:\n```bash\naiwg daemon-init orchestrator\n```\n\n**Response**: \"Daemon initialized with `orchestrator` profile. High-authority orchestration settings applied. Config at `.aiwg\u002Fdaemon\u002Fconfig.yaml`. The orchestrator profile enables `aiwg mc` (Mission Control) dispatch patterns.\"\n\n---\n\n### Example 3: Force reinitialize\n\n**User**: \"Reinitialize the daemon — the old config is stale\"\n\n**Extraction**: Force reinit, no profile specified — use `manager` with `--force`\n\n**Action**:\n```bash\naiwg daemon-init --force\n```\n\n**Response**: \"Daemon config overwritten with `manager` profile. Previous config backed up to `.aiwg\u002Fdaemon\u002Fconfig.yaml.bak`.\"\n\n---\n\n### Example 4: Worker for CI pipeline\n\n**User**: \"I need a worker daemon for running background test loops in CI\"\n\n**Extraction**: Init with `worker` profile\n\n**Action**:\n```bash\naiwg daemon-init worker\n```\n\n**Response**: \"Daemon initialized with `worker` profile. Minimal decision authority configured — this profile executes tasks and reports results without autonomous orchestration. Suitable for CI background loops.\"\n\n## Clarification Prompts\n\nIf the user's intent is ambiguous:\n\n- \"Which daemon profile should I use? Options: `manager` (default), `orchestrator`, `worker`, `monitor`\"\n- \"A daemon config already exists at `.aiwg\u002Fdaemon\u002Fconfig.yaml`. Should I overwrite it with `--force`?\"\n- \"Are you initializing for a new project, or reconfiguring an existing daemon?\"\n\n## References\n\n- @$AIWG_ROOT\u002Fsrc\u002Fcli\u002Fhandlers\u002Fdaemon.ts — Daemon command handler\n- @$AIWG_ROOT\u002Fdocs\u002Fdaemon-guide.md — Full daemon documentation including session launch\n- @$AIWG_ROOT\u002Fdocs\u002Fmessaging-guide.md — Messaging integration (Telegram, Slack) configuration\n- @$AIWG_ROOT\u002Fdocs\u002Fcli-reference.md — CLI reference\n","# Daemon Init\n\nYou initialize AIWG daemon mode configuration from a named profile. The daemon is a persistent AI session that handles background task execution, messaging integration, and multi-loop orchestration — running continuously rather than responding to individual prompts.\n\n## Triggers\n\nAlternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):\n\n- \"start daemon mode\" → init with default profile\n- \"set up background agent\" → init with manager profile\n- \"configure aiwg for continuous operation\" → init with orchestrator profile\n- \"i want aiwg running in the background\" → init with manager profile\n- \"reinitialize daemon\" → init with `--force`\n\n## Trigger Patterns Reference\n\n| Pattern | Example | Action |\n|---------|---------|--------|\n| Default init | \"initialize daemon\" | Run `aiwg daemon-init` |\n| Named profile | \"init daemon as orchestrator\" | Run `aiwg daemon-init orchestrator` |\n| Force reinit | \"reinitialize daemon config\" | Run `aiwg daemon-init --force` |\n| Worker mode | \"set up a worker daemon\" | Run `aiwg daemon-init worker` |\n| Monitor mode | \"run daemon in monitoring mode\" | Run `aiwg daemon-init monitor` |\n\n## Behavior\n\nWhen triggered:\n\n1. **Extract intent**:\n   - Is a profile name specified? Default to `manager` if not.\n   - Is `--force` needed (user mentioned reinitializing or overwriting)?\n\n2. **Select the appropriate profile**:\n\n   | Profile | Authority | Use Case |\n   |---------|-----------|----------|\n   | `manager` (default) | Balanced — orchestrate and execute | General-purpose persistent agent |\n   | `orchestrator` | High — coordinate other agents | Driving multi-agent workflows |\n   | `worker` | Low — execute, minimal decisions | Background task execution |\n   | `monitor` | Read-only — observe and alert | Ops monitoring, health checks |\n\n3. **Run the command**:\n\n   ```bash\n   # Default profile (manager)\n   aiwg daemon-init\n\n   # Named profile\n   aiwg daemon-init orchestrator\n   aiwg daemon-init worker\n   aiwg daemon-init monitor\n\n   # Overwrite existing config\n   aiwg daemon-init --force\n   aiwg daemon-init orchestrator --force\n   ```\n\n4. **Know where config is written**: `.aiwg\u002Fdaemon\u002Fconfig.yaml` in the current project. This file controls:\n   - Session persistence behavior\n   - Messaging integration endpoints (Telegram, Slack, etc.)\n   - Task queue and loop settings\n   - Authority level and decision boundaries\n\n5. **Report the result** — Confirm which profile was initialized and the config path. If daemon is already initialized, remind the user to use `--force` to overwrite.\n\n## Examples\n\n### Example 1: Default initialization\n\n**User**: \"Set up daemon mode\"\n\n**Extraction**: Init request, no profile specified — use `manager`\n\n**Action**:\n```bash\naiwg daemon-init\n```\n\n**Response**: \"Daemon initialized with `manager` profile. Config written to `.aiwg\u002Fdaemon\u002Fconfig.yaml`. To start the daemon, see `docs\u002Fdaemon-guide.md` for session launch instructions.\"\n\n---\n\n### Example 2: Orchestrator profile\n\n**User**: \"Initialize the daemon as an orchestrator — I want it coordinating multiple sub-agents\"\n\n**Extraction**: Init with `orchestrator` profile\n\n**Action**:\n```bash\naiwg daemon-init orchestrator\n```\n\n**Response**: \"Daemon initialized with `orchestrator` profile. High-authority orchestration settings applied. Config at `.aiwg\u002Fdaemon\u002Fconfig.yaml`. The orchestrator profile enables `aiwg mc` (Mission Control) dispatch patterns.\"\n\n---\n\n### Example 3: Force reinitialize\n\n**User**: \"Reinitialize the daemon — the old config is stale\"\n\n**Extraction**: Force reinit, no profile specified — use `manager` with `--force`\n\n**Action**:\n```bash\naiwg daemon-init --force\n```\n\n**Response**: \"Daemon config overwritten with `manager` profile. Previous config backed up to `.aiwg\u002Fdaemon\u002Fconfig.yaml.bak`.\"\n\n---\n\n### Example 4: Worker for CI pipeline\n\n**User**: \"I need a worker daemon for running background test loops in CI\"\n\n**Extraction**: Init with `worker` profile\n\n**Action**:\n```bash\naiwg daemon-init worker\n```\n\n**Response**: \"Daemon initialized with `worker` profile. Minimal decision authority configured — this profile executes tasks and reports results without autonomous orchestration. Suitable for CI background loops.\"\n\n## Clarification Prompts\n\nIf the user's intent is ambiguous:\n\n- \"Which daemon profile should I use? Options: `manager` (default), `orchestrator`, `worker`, `monitor`\"\n- \"A daemon config already exists at `.aiwg\u002Fdaemon\u002Fconfig.yaml`. Should I overwrite it with `--force`?\"\n- \"Are you initializing for a new project, or reconfiguring an existing daemon?\"\n\n## References\n\n- @$AIWG_ROOT\u002Fsrc\u002Fcli\u002Fhandlers\u002Fdaemon.ts — Daemon command handler\n- @$AIWG_ROOT\u002Fdocs\u002Fdaemon-guide.md — Full daemon documentation including session launch\n- @$AIWG_ROOT\u002Fdocs\u002Fmessaging-guide.md — Messaging integration (Telegram, Slack) configuration\n- @$AIWG_ROOT\u002Fdocs\u002Fcli-reference.md — CLI reference\n",{"name":5,"namespace":39,"platforms":40,"description":7},"aiwg",[41],"all","main","6754967c344ccb087a8de06972f55a41067b291b","agentic\u002Fcode\u002Fplugins\u002Futils\u002Fskills\u002Fdaemon-init",36,"https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg","https:\u002F\u002Faiwg.io","https:\u002F\u002Fgithub.com\u002Fjmagly","https:\u002F\u002Fintegrolabs.io","ml\u002Fai, industrial automation, safety\u002Fsecurity, ssi\r\n\r\nmagly.net\r\nintegrolabs.io\r\naiwg.io\r\nfortemi.com\r\npagenary.com\r\nbytecask.com","2026-11-14 02:10:01",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add jmagly\u002Faiwg --skill daemon-init",{"tool":58,"command":59},"bunx","bunx skills add jmagly\u002Faiwg --skill daemon-init",{"tool":61,"command":62},"pnpm","pnpm dlx skills add jmagly\u002Faiwg --skill daemon-init","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Futils\u002Fskills\u002Fdaemon-init\u002FSKILL.md",true,[],[67,95,119,125,132,146],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":74,"publishedAt":34},"01M70QA0BSYJ49EES9V4RE8QH1","host-hardening","Read-only system hardening baseline and plan-first host hardening recommendations for SSH, Docker bind addresses, firewall persistence, datastores, exporters and audit retention.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fsecurity-engineering\u002Fskills\u002Fhost-hardening\u002FSKILL.md",[73],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94],"host","host hardening","hardening","read","re","recommendations","remediation","plan","port","verification","Bash","access","only","retention","audit","never","firewall","bind","secrets","request",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":105,"publishedAt":34},"01M70PNT2Z4HMZPRBTAF6073NN","exposure-analysis","Read-only firewall analysis and effective host exposure reconstruction for Docker published ports, UFW bypass, stale rules, CDN scope, IPv6 asymmetry and external probe allowlists.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fforensics\u002Fskills\u002Fexposure-analysis\u002FSKILL.md",[101,104],{"categoryNo":102,"categoryName":103,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[106,107,108,78,109,83,110,111,85,112,75,113,87,114,115,90,91,116,117,118],"exposure analysis","analysis","unknown","credentials","collection","ufw","ports","internet","local","scope","reconstruction","operator","write",{"skillNo":120,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":124,"publishedAt":34},"01M70P8QATMPKA78E4FT5D2TNA","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsecurity-engineering\u002Fskills\u002Fhost-hardening\u002FSKILL.md",[123],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[77,75,76,86,78,94,81,80,89,82,83,84,85,93,87,88,79,90,91,92],{"skillNo":126,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":131,"publishedAt":34},"01M70NMPVJ5H0JH131P60FW4R8","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fforensics-complete\u002Fskills\u002Fexposure-analysis\u002FSKILL.md",[129,130],{"categoryNo":102,"categoryName":103,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[107,106,90,109,83,110,85,108,75,113,87,114,115,78,91,112,111,116,117,118],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":139,"publishedAt":34},"01M6CB4DDR0B4NNCFK7ZK7449H","fixture-skill","Exercise rule delivery.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Frule-delivery\u002Fskills\u002Ffixture-skill\u002FSKILL.md",[138],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[140,141,142,143,144,145],"fixture skill","fixture","rule","delivery","true","exercise",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":153,"publishedAt":34},"01M6CB4AVK1W76MFMPP0JP32CJ","pi-local","Pi-local duplicate-precedence fixture.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fproviders\u002Fpi\u002Fproject\u002F.pi\u002Fskills\u002Fpi-local\u002FSKILL.md",[152],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[154,155,114,156,141],"pi","pi local","duplicate"]