[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AD4MVFP06VR8HZMJ71YZJ9":3,"skill-same:01M6AD4MVFP06VR8HZMJ71YZJ9":69},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":44,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M6AD4MVFP06VR8HZMJ71YZJ9","custom-engine-implementation",null,"Add and test declarative behavior-defined agentic engines in gh-aw, extending Go infrastructure only when necessary.","github\u002Fgh-aw","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3VCZ4WKQSFSRTPN7N9DN",5636,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcustom-engine-implementation\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"custom engine implementation","engine","implementation","custom","go","agentic","test","infrastructure","gh","behavior","only","add","declarative","when","extending","2026-11-10 10:12:30",false,"---\nname: custom-engine-implementation\ndescription: Add and test declarative behavior-defined agentic engines in gh-aw, extending Go infrastructure only when necessary.\n---\n\n# Custom Engine Implementation\n\nUse this skill when adding a new agentic engine definition or extending the\nbehavior-defined engine infrastructure.\n\n## Choose the smallest implementation\n\nPrefer a shared Markdown engine definition. Installation, execution, MCP\nconfiguration, provider routing, caching, manifests, plugins, network defaults,\nharness scripts, and log parsing can already be declared through\n`engine.behaviors`.\n\nOnly change Go code when the engine needs a reusable behavior that the\ndeclarative model cannot express. Add a dedicated Go engine only when the\nshared behavior-defined runtime cannot run the engine at all.\n\n| Need | Implementation |\n|---|---|\n| Existing behaviors are sufficient | Add an imported shared engine definition |\n| A reusable declarative behavior is missing | Extend the definition model and behavior-defined runtime |\n| The shared runtime is fundamentally unsuitable | Add a dedicated Go engine and register it |\n\nThe relevant implementation is in:\n\n- `pkg\u002Fworkflow\u002Fengine_definition.go` for the definition model and catalog\n- `pkg\u002Fworkflow\u002Fbehavior_defined_engine.go` for the shared runtime\n- `pkg\u002Fworkflow\u002Fengine_definition_loader.go` for embedded built-in definitions\n- `pkg\u002Fworkflow\u002Fagentic_engine.go` for dedicated Go engine registration\n- `pkg\u002Fparser\u002Fschemas\u002Fmain_workflow_schema.json` for the workflow schema\n\n## Study representative engines\n\nRead the closest examples before making changes:\n\n- `.github\u002Fworkflows\u002Fshared\u002Fopencode.md`: npm installation, merged\n  configuration, MCP, provider routing, and log parsing\n- `.github\u002Fworkflows\u002Fshared\u002Faider.md`: Python installation and a custom harness\n  without native MCP\n- `.github\u002Fworkflows\u002Fshared\u002Fcrush.md`: native MCP configuration adapter and\n  harness\n- `.github\u002Fworkflows\u002Fshared\u002Fcursor.md`: plugin support\n- `.github\u002Fworkflows\u002Fshared\u002Fdeepseek-harness.md`: provider endpoint discovery\n  and a headless profile\n\nUse the examples to identify a pattern, not as a reason to copy optional\nbehaviors.\n\n## Add a shared engine definition\n\n1. Create `.github\u002Fworkflows\u002Fshared\u002F\u003Cengine>.md`.\n2. Declare `engine.id`, `display-name`, `description`, `experimental`, provider\n   metadata, authentication, and only the required `behaviors`.\n3. Pin a default CLI version. Make installation deterministic and provide a\n   verification command.\n4. Document setup, authentication, model syntax, MCP support, and limitations\n   in the Markdown body. Keep in-repository integrations clearly identified as\n   unsupported samples.\n5. Add the engine ID and shared definition path to\n   `.github\u002Faw\u002Fengines.json`. Imported behavior-defined engines are registered\n   dynamically; do not add them to `NewEngineRegistry()`.\n6. Add `.github\u002Fworkflows\u002Fsmoke-\u003Cengine>.md`, following the closest existing\n   smoke workflow. Import the shared definition and exercise the capabilities\n   the engine claims to support.\n7. Update the unsupported sample table in\n   `docs\u002Fsrc\u002Fcontent\u002Fdocs\u002Freference\u002Fengines.md`.\n8. Add a changeset when the engine is a user-visible repository sample. New\n   experimental engines have precedent as a `minor` change.\n9. Run `make recompile` and include the generated smoke workflow\n   `.lock.yml`.\n\n`TestKnownEngineImportsFile_MatchesSharedEngineFiles` in\n`pkg\u002Fworkflow\u002Fengine_definition_test.go` enforces catalog coverage for shared\nexternal engines.\n\n## Design the definition\n\nKeep the definition declarative and minimal:\n\n- Select the correct package manager, package name, binary name, version, and\n  verification command under `behaviors.installation`.\n- Put invocation arguments and non-secret environment variables under\n  `behaviors.execution`.\n- Use an existing secret strategy and provider environment mode where\n  possible.\n- Declare native MCP support only when the CLI can consume the generated\n  configuration. Otherwise use a harness or the gh-aw CLI proxy pattern.\n- Add only required default domains and map provider-specific domains under\n  `behaviors.network.provider-domains`.\n- Declare manifest files, cache paths, and plugin support only when the CLI\n  consumes them.\n- Add a log parser only when its emitted event format can be tested.\n\nTreat inline JavaScript in harnesses, configuration adapters, and log parsers\nas production code. Avoid shell interpolation, validate paths and child-process\narguments, preserve nonzero exit codes, and never print secret values. Enabling\npackage lifecycle scripts requires a pinned version and an explicit reason.\n\nFor log and error regular expressions, also load\n`.github\u002Fskills\u002Ferror-pattern-safety\u002FSKILL.md`.\n\n## Extend declarative infrastructure\n\nWhen an engine exposes a generally useful capability that existing behaviors\ncannot express:\n\n1. Add the smallest field to the types in\n   `pkg\u002Fworkflow\u002Fengine_definition.go`.\n2. Validate and render it in the focused behavior-defined engine files.\n3. Update `pkg\u002Fparser\u002Fschemas\u002Fmain_workflow_schema.json`.\n4. Add focused tests for parsing, validation, and rendered execution behavior.\n5. Run `make generate-schema-docs` when generated schema documentation changes.\n\nDo not add a schema field for a behavior that can be represented by existing\ninstallation, execution, environment, harness, or adapter fields.\n\nFor a dedicated Go runtime, implement the engine interfaces by composing the\nexisting helpers, keep engine-specific code in its own files, and register the\nengine in `pkg\u002Fworkflow\u002Fagentic_engine.go`. Cover configuration, commands,\nenvironment, authentication, tools, logs, and failure handling with focused\ntests.\n\n## Test the right layers\n\nUse tests that match the changed behavior:\n\n| Area | Tests and examples |\n|---|---|\n| Harness, configuration, MCP, and environment | `behavior_defined_engine_harness_test.go` |\n| Log parsing | `behavior_defined_engine_log_parser_test.go` |\n| Cache behavior | `behavior_defined_engine_cache_test.go` |\n| Definitions, catalog, and known imports | `engine_definition_test.go`, `engine_catalog_test.go` |\n| Embedded definitions | `engine_definition_loader_test.go` |\n| Real shared workflow harness | `aider_workflow_test.go` |\n| Sandboxed CLI visibility | `cloud_hypervisor_test.go` |\n| Generated smoke workflows | `compiled_lock_files_test.go` |\n\nTest both definition parsing and the generated installation\u002Fexecution steps.\nInclude negative cases for unsafe paths, invalid configuration, missing\ncredentials, or malformed logs when relevant.\n\n## Validate\n\nAfter Go changes:\n\n```bash\nmake build\nmake fmt\n```\n\nAfter workflow Markdown changes:\n\n```bash\nmake recompile\n```\n\nRun focused `go test` commands for the changed behavior while iterating. Before\nan intermediate progress report, run:\n\n```bash\nmake agent-report-progress-no-test\n```\n\nBefore the final progress report, run:\n\n```bash\nmake agent-report-progress\n```\n\nUse `make agent-finish` for the final repository validation when time allows.\nDo not trigger a smoke workflow from a Copilot cloud agent run.\n\n## Completion checklist\n\n- The declarative path was preferred unless its limitations are documented.\n- The engine definition uses a pinned, verified installation.\n- Authentication, provider\u002Fmodel handling, MCP, and network access are covered.\n- Harnesses and adapters do not expose secrets or interpolate untrusted input.\n- `.github\u002Faw\u002Fengines.json`, smoke workflow, generated lock file,\n  documentation, and changeset are updated when applicable.\n- Focused tests cover parsing and rendered runtime behavior.\n- Repository validation passes.\n","# Custom Engine Implementation\n\nUse this skill when adding a new agentic engine definition or extending the\nbehavior-defined engine infrastructure.\n\n## Choose the smallest implementation\n\nPrefer a shared Markdown engine definition. Installation, execution, MCP\nconfiguration, provider routing, caching, manifests, plugins, network defaults,\nharness scripts, and log parsing can already be declared through\n`engine.behaviors`.\n\nOnly change Go code when the engine needs a reusable behavior that the\ndeclarative model cannot express. Add a dedicated Go engine only when the\nshared behavior-defined runtime cannot run the engine at all.\n\n| Need | Implementation |\n|---|---|\n| Existing behaviors are sufficient | Add an imported shared engine definition |\n| A reusable declarative behavior is missing | Extend the definition model and behavior-defined runtime |\n| The shared runtime is fundamentally unsuitable | Add a dedicated Go engine and register it |\n\nThe relevant implementation is in:\n\n- `pkg\u002Fworkflow\u002Fengine_definition.go` for the definition model and catalog\n- `pkg\u002Fworkflow\u002Fbehavior_defined_engine.go` for the shared runtime\n- `pkg\u002Fworkflow\u002Fengine_definition_loader.go` for embedded built-in definitions\n- `pkg\u002Fworkflow\u002Fagentic_engine.go` for dedicated Go engine registration\n- `pkg\u002Fparser\u002Fschemas\u002Fmain_workflow_schema.json` for the workflow schema\n\n## Study representative engines\n\nRead the closest examples before making changes:\n\n- `.github\u002Fworkflows\u002Fshared\u002Fopencode.md`: npm installation, merged\n  configuration, MCP, provider routing, and log parsing\n- `.github\u002Fworkflows\u002Fshared\u002Faider.md`: Python installation and a custom harness\n  without native MCP\n- `.github\u002Fworkflows\u002Fshared\u002Fcrush.md`: native MCP configuration adapter and\n  harness\n- `.github\u002Fworkflows\u002Fshared\u002Fcursor.md`: plugin support\n- `.github\u002Fworkflows\u002Fshared\u002Fdeepseek-harness.md`: provider endpoint discovery\n  and a headless profile\n\nUse the examples to identify a pattern, not as a reason to copy optional\nbehaviors.\n\n## Add a shared engine definition\n\n1. Create `.github\u002Fworkflows\u002Fshared\u002F\u003Cengine>.md`.\n2. Declare `engine.id`, `display-name`, `description`, `experimental`, provider\n   metadata, authentication, and only the required `behaviors`.\n3. Pin a default CLI version. Make installation deterministic and provide a\n   verification command.\n4. Document setup, authentication, model syntax, MCP support, and limitations\n   in the Markdown body. Keep in-repository integrations clearly identified as\n   unsupported samples.\n5. Add the engine ID and shared definition path to\n   `.github\u002Faw\u002Fengines.json`. Imported behavior-defined engines are registered\n   dynamically; do not add them to `NewEngineRegistry()`.\n6. Add `.github\u002Fworkflows\u002Fsmoke-\u003Cengine>.md`, following the closest existing\n   smoke workflow. Import the shared definition and exercise the capabilities\n   the engine claims to support.\n7. Update the unsupported sample table in\n   `docs\u002Fsrc\u002Fcontent\u002Fdocs\u002Freference\u002Fengines.md`.\n8. Add a changeset when the engine is a user-visible repository sample. New\n   experimental engines have precedent as a `minor` change.\n9. Run `make recompile` and include the generated smoke workflow\n   `.lock.yml`.\n\n`TestKnownEngineImportsFile_MatchesSharedEngineFiles` in\n`pkg\u002Fworkflow\u002Fengine_definition_test.go` enforces catalog coverage for shared\nexternal engines.\n\n## Design the definition\n\nKeep the definition declarative and minimal:\n\n- Select the correct package manager, package name, binary name, version, and\n  verification command under `behaviors.installation`.\n- Put invocation arguments and non-secret environment variables under\n  `behaviors.execution`.\n- Use an existing secret strategy and provider environment mode where\n  possible.\n- Declare native MCP support only when the CLI can consume the generated\n  configuration. Otherwise use a harness or the gh-aw CLI proxy pattern.\n- Add only required default domains and map provider-specific domains under\n  `behaviors.network.provider-domains`.\n- Declare manifest files, cache paths, and plugin support only when the CLI\n  consumes them.\n- Add a log parser only when its emitted event format can be tested.\n\nTreat inline JavaScript in harnesses, configuration adapters, and log parsers\nas production code. Avoid shell interpolation, validate paths and child-process\narguments, preserve nonzero exit codes, and never print secret values. Enabling\npackage lifecycle scripts requires a pinned version and an explicit reason.\n\nFor log and error regular expressions, also load\n`.github\u002Fskills\u002Ferror-pattern-safety\u002FSKILL.md`.\n\n## Extend declarative infrastructure\n\nWhen an engine exposes a generally useful capability that existing behaviors\ncannot express:\n\n1. Add the smallest field to the types in\n   `pkg\u002Fworkflow\u002Fengine_definition.go`.\n2. Validate and render it in the focused behavior-defined engine files.\n3. Update `pkg\u002Fparser\u002Fschemas\u002Fmain_workflow_schema.json`.\n4. Add focused tests for parsing, validation, and rendered execution behavior.\n5. Run `make generate-schema-docs` when generated schema documentation changes.\n\nDo not add a schema field for a behavior that can be represented by existing\ninstallation, execution, environment, harness, or adapter fields.\n\nFor a dedicated Go runtime, implement the engine interfaces by composing the\nexisting helpers, keep engine-specific code in its own files, and register the\nengine in `pkg\u002Fworkflow\u002Fagentic_engine.go`. Cover configuration, commands,\nenvironment, authentication, tools, logs, and failure handling with focused\ntests.\n\n## Test the right layers\n\nUse tests that match the changed behavior:\n\n| Area | Tests and examples |\n|---|---|\n| Harness, configuration, MCP, and environment | `behavior_defined_engine_harness_test.go` |\n| Log parsing | `behavior_defined_engine_log_parser_test.go` |\n| Cache behavior | `behavior_defined_engine_cache_test.go` |\n| Definitions, catalog, and known imports | `engine_definition_test.go`, `engine_catalog_test.go` |\n| Embedded definitions | `engine_definition_loader_test.go` |\n| Real shared workflow harness | `aider_workflow_test.go` |\n| Sandboxed CLI visibility | `cloud_hypervisor_test.go` |\n| Generated smoke workflows | `compiled_lock_files_test.go` |\n\nTest both definition parsing and the generated installation\u002Fexecution steps.\nInclude negative cases for unsafe paths, invalid configuration, missing\ncredentials, or malformed logs when relevant.\n\n## Validate\n\nAfter Go changes:\n\n```bash\nmake build\nmake fmt\n```\n\nAfter workflow Markdown changes:\n\n```bash\nmake recompile\n```\n\nRun focused `go test` commands for the changed behavior while iterating. Before\nan intermediate progress report, run:\n\n```bash\nmake agent-report-progress-no-test\n```\n\nBefore the final progress report, run:\n\n```bash\nmake agent-report-progress\n```\n\nUse `make agent-finish` for the final repository validation when time allows.\nDo not trigger a smoke workflow from a Copilot cloud agent run.\n\n## Completion checklist\n\n- The declarative path was preferred unless its limitations are documented.\n- The engine definition uses a pinned, verified installation.\n- Authentication, provider\u002Fmodel handling, MCP, and network access are covered.\n- Harnesses and adapters do not expose secrets or interpolate untrusted input.\n- `.github\u002Faw\u002Fengines.json`, smoke workflow, generated lock file,\n  documentation, and changeset are updated when applicable.\n- Focused tests cover parsing and rendered runtime behavior.\n- Repository validation passes.\n",{"name":5,"description":7},"main","8541229759617347888641eba917d3b0ad66a984",".github\u002Fskills\u002Fcustom-engine-implementation",626,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw","https:\u002F\u002Fgh.io\u002Fgh-aw","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-15 06:45:15",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add github\u002Fgh-aw --skill custom-engine-implementation",{"tool":55,"command":56},"bunx","bunx skills add github\u002Fgh-aw --skill custom-engine-implementation",{"tool":58,"command":59},"pnpm","pnpm dlx skills add github\u002Fgh-aw --skill custom-engine-implementation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcustom-engine-implementation\u002FSKILL.md",true,[63],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"agents\u002Fopenai.yaml","REFERENCE","参考文档",99,"https:\u002F\u002Fgithub.com\u002Ffeniix\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fsetup-pre-commit\u002Fagents\u002Fopenai.yaml",[70,78,86,113,131,155],{"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":77},"01M7DQYVZ9W9DDXKQ9452SNP8J","cracktro","Edit, preview, and verify the standalone interactive talk deck in docs\u002Fpublic\u002Fcracktro (slides, SVG diagrams, transitions, WebAudio sound).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcracktro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":85},"01M7612HQ4378TK8QZ5HPAF4KR","create-connector","Create or extend a declaration-only third-party connector, with narrow reads, separate safe outputs, optional protected triggers, and offline conformance evidence.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcreate-connector\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":100,"publishedAt":34},"01M6ADC942STTXHFV410J4DH0X","GitHub Agentic Workflows","GitHub Agentic Workflows (`gh-aw`) is a GitHub CLI extension for writing Agentic Workflows in markdown and compiling them to GitHub Actions.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002FSKILL.md",[92,97],{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":98,"categoryName":99,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000023","Skill与智能体开发",[9,101,102,103,24,104,105,106,107,27,108,109,110,111,112],"github agentic workflows","agentic workflows","workflows","extension","markdown","github cli","cli","for","compiling","writing","github actions","actions",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":34},"01M6ADC6ZXSA46N9XD6VNAP1MS","windows-compatibility","Cross-platform path handling and command patterns","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fwindows-compatibility\u002FSKILL.md",[],[120,121,122,123,124,125,126,127,128,129,130],"windows","windows compatibility","compatibility","command","git","bugs","platform","high","patterns","cross-platform","path",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":34},"01M6ADC44957SVQF96R5YY247P","versioning-policy","Semver versioning rules for Squad SDK and CLI — prevents prerelease version incidents","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fversioning-policy\u002FSKILL.md",[],[138,139,140,141,21,107,142,143,144,145,146,147,148,149,108,150,151,152,153,154],"versioning","policy","versioning policy","gate","workspace","pr","sdk","release","ci","npm","semver","squad","incident","incidents","Rules","version","resolution",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":165,"publishedAt":34},"01M6ADC1PHMEAEVR87F8PDR89X","tiered-memory","Three-tier agent memory model (hot\u002Fcold\u002Fwiki) for context reduction per spawn","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Ftiered-memory\u002FSKILL.md",[161,164],{"categoryNo":162,"categoryName":163,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":98,"categoryName":99,"taxonomyType":95,"taxonomyTypeDesc":96},[166,167,168,169,170,171,172,173,174,175,176,177,178,108,179,180],"tiered memory","memory","performance","design","agent memory","proposal","cold","model","wiki","spawn","memory-management","context","three","runtime","management"]