[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GV3FFFB53DESV2C1DTCYWG":3,"skill-same:01M6GV3FFFB53DESV2C1DTCYWG":74},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":14,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M6GV3FFFB53DESV2C1DTCYWG","manage-accounts",null,"Connect, discover, create, select, review, and revoke online accounts through the local Elegy Accounts broker, and request least-privilege access for Codex or Holon agents without exposing credentials. Use when an agent needs an account for research, client work, deployment, email, cloud infrastructure, source control, or another provider-backed action; when a user asks what accounts are connected; or when auth, CAPTCHA, MFA, consent, terms, payment, identity verification, or account selection blocks a workflow.","Sofreshx\u002FElegy","Sofreshx","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F46634397?v=4","01M6GV3ACQ2VKGTY22KKQDDPPG","Sfrsh","01M6GV3AYZA1GPCMY0JP2PQSVC",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSofreshx\u002FElegy\u002Fblob\u002Fmain\u002Fplugins\u002Faccounts\u002Fskills\u002Felegy-manage-accounts\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"manage accounts","manage","work","broker","captcha","discover","local","selection","provider","use","review","select","access","email","verification","create","connect","deployment","auth","workflow","2026-11-10 10:12:30",false,"---\nname: manage-accounts\ndescription: Connect, discover, create, select, review, and revoke online accounts through the local Elegy Accounts broker, and request least-privilege access for Codex or Holon agents without exposing credentials. Use when an agent needs an account for research, client work, deployment, email, cloud infrastructure, source control, or another provider-backed action; when a user asks what accounts are connected; or when auth, CAPTCHA, MFA, consent, terms, payment, identity verification, or account selection blocks a workflow.\n---\n\n# Manage accounts\n\nUse the `elegy-accounts` MCP tools. Treat account metadata, grants, leases, and request status as safe agent data. Treat credentials, OAuth codes, browser sessions, and provider tokens as broker-only data.\n\n## Resolve access\n\n1. State the concrete purpose and smallest named operations required by the downstream tool, such as `dns.records.read` or `deployments.create`.\n2. Call `account_require` with provider, purpose, operations, and an account ID only when the user already selected one.\n3. If an account is available, call `account_request_access`. Never widen operations to avoid a later approval.\n4. If interaction is required, call `account_discover` and explain the runtime provider-pack choices. Use `account_present` with the request ID so Account Center opens at the exact durable checkpoint. Fall back to `account_open_center` only when there is no request yet.\n5. If no suitable account exists and creation is appropriate, call `account_request_creation` with purpose and user constraints. Use `account_attention_list` to recover durable work. Poll only when useful with `account_request_status`; do not busy-wait.\n6. Continue the original task only after the request reports approved\u002Fconnected and the downstream provider tool accepts the capability.\n\nFor bundled GitHub and Cloudflare reads, use the typed `elegy-account-actions` tools after account resolution. The action host reuses an active read grant, requests one durable approval when needed, and keeps the credential and lease inside the broker. Never ask the user to reconnect merely because a new Codex session started.\n\n## Human checkpoints\n\nStop automation and hand control to the person for CAPTCHA, MFA, terms, payment, KYC\u002Fidentity verification, ambiguous plans, unexpected pages, or provider consent. Explain exactly what is waiting and how the agent will resume. Never click through, accept, solve, or bypass these boundaries without the user's direct action where policy permits.\n\n## Browser discovery\n\nDescribe Brave discovery as \"continue with your signed-in browser.\" It is an unverified hint until the broker validates provider identity. Never claim that Elegy imports saved passwords or cookies. Never ask the user to paste a password, session cookie, OAuth code, refresh token, or API token into chat. When a provider requires a limited token, direct capture to Account Center or the Elegy Brave extension.\n\n## Multiple accounts and revocation\n\nWhen more than one identity matches, show sanitized provider identities and ask the user to select; do not guess. Use `account_revoke_grant` when requested or when access is no longer needed. Use `account_audit_list` to explain a decision or failure without requesting secret diagnostics.\n\nRead [references\u002Fprovider-modes.md](references\u002Fprovider-modes.md) only when choosing between connection methods. Pack authors use [the provider-pack contract](..\u002F..\u002Fdocs\u002Fprovider-packs.md).\n","# Manage accounts\n\nUse the `elegy-accounts` MCP tools. Treat account metadata, grants, leases, and request status as safe agent data. Treat credentials, OAuth codes, browser sessions, and provider tokens as broker-only data.\n\n## Resolve access\n\n1. State the concrete purpose and smallest named operations required by the downstream tool, such as `dns.records.read` or `deployments.create`.\n2. Call `account_require` with provider, purpose, operations, and an account ID only when the user already selected one.\n3. If an account is available, call `account_request_access`. Never widen operations to avoid a later approval.\n4. If interaction is required, call `account_discover` and explain the runtime provider-pack choices. Use `account_present` with the request ID so Account Center opens at the exact durable checkpoint. Fall back to `account_open_center` only when there is no request yet.\n5. If no suitable account exists and creation is appropriate, call `account_request_creation` with purpose and user constraints. Use `account_attention_list` to recover durable work. Poll only when useful with `account_request_status`; do not busy-wait.\n6. Continue the original task only after the request reports approved\u002Fconnected and the downstream provider tool accepts the capability.\n\nFor bundled GitHub and Cloudflare reads, use the typed `elegy-account-actions` tools after account resolution. The action host reuses an active read grant, requests one durable approval when needed, and keeps the credential and lease inside the broker. Never ask the user to reconnect merely because a new Codex session started.\n\n## Human checkpoints\n\nStop automation and hand control to the person for CAPTCHA, MFA, terms, payment, KYC\u002Fidentity verification, ambiguous plans, unexpected pages, or provider consent. Explain exactly what is waiting and how the agent will resume. Never click through, accept, solve, or bypass these boundaries without the user's direct action where policy permits.\n\n## Browser discovery\n\nDescribe Brave discovery as \"continue with your signed-in browser.\" It is an unverified hint until the broker validates provider identity. Never claim that Elegy imports saved passwords or cookies. Never ask the user to paste a password, session cookie, OAuth code, refresh token, or API token into chat. When a provider requires a limited token, direct capture to Account Center or the Elegy Brave extension.\n\n## Multiple accounts and revocation\n\nWhen more than one identity matches, show sanitized provider identities and ask the user to select; do not guess. Use `account_revoke_grant` when requested or when access is no longer needed. Use `account_audit_list` to explain a decision or failure without requesting secret diagnostics.\n\nRead [references\u002Fprovider-modes.md](references\u002Fprovider-modes.md) only when choosing between connection methods. Pack authors use [the provider-pack contract](..\u002F..\u002Fdocs\u002Fprovider-packs.md).\n",{"name":5,"description":7},"main","cdaaaccc462c986f4a2c0032b75698f15c71f62b","plugins\u002Faccounts\u002Fskills\u002Felegy-manage-accounts","https:\u002F\u002Fgithub.com\u002FSofreshx\u002FElegy","https:\u002F\u002Fgithub.com\u002FSofreshx","2026-11-02 22:33:10",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add Sofreshx\u002FElegy --skill manage-accounts",{"tool":56,"command":57},"bunx","bunx skills add Sofreshx\u002FElegy --skill manage-accounts",{"tool":59,"command":60},"pnpm","pnpm dlx skills add Sofreshx\u002FElegy --skill manage-accounts","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSofreshx\u002FElegy\u002Fblob\u002Fmain\u002Fplugins\u002Faccounts\u002Fskills\u002Felegy-manage-accounts\u002FSKILL.md",true,[64,70],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"agents\u002Fopenai.yaml","REFERENCE","参考文档",434,"https:\u002F\u002Fgithub.com\u002FSofreshx\u002FElegy\u002Fblob\u002Fmain\u002Fplugins\u002Faccounts\u002Fskills\u002Felegy-manage-accounts\u002Fagents\u002Fopenai.yaml",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fprovider-modes.md",1347,"https:\u002F\u002Fgithub.com\u002FSofreshx\u002FElegy\u002Fblob\u002Fmain\u002Fplugins\u002Faccounts\u002Fskills\u002Felegy-manage-accounts\u002Freferences\u002Fprovider-modes.md",[75,95,115,141,160,176],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":86,"publishedAt":39},"01M6GV77GEYNKPE96EFA282AY0","elegy-skill-authoring","Doctrine for drafting, auditing, and fixing Elegy skills. Use when creating a new skill, running an audit against an existing one, or triaging structural and content findings.","https:\u002F\u002Fgithub.com\u002FSofreshx\u002FElegy\u002Fblob\u002Fmain\u002Fskills\u002Felegy-skill-authoring\u002FSKILL.md",[81],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[87,88,89,90,91,28,92,93,94],"elegy skill authoring","authoring","skill authoring","content","audit","doctrine","new skill","structural",{"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":104,"publishedAt":39},"01M6GV6VG31WQVTQ0RGEEEWKQ8","elegy-plugin-authoring","Use when creating or reviewing an Elegy system-adapter plugin that connects an agent to a data source, database, platform, API, local system, or executable boundary.","https:\u002F\u002Fgithub.com\u002FSofreshx\u002FElegy\u002Fblob\u002Fmain\u002Fskills\u002Felegy-plugin-authoring\u002FSKILL.md",[101],{"categoryNo":102,"categoryName":103,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000010","后端与接口",[105,106,88,107,108,109,110,111,112,28,25,113,114],"plugin","plugin authoring","elegy plugin authoring","database","data","boundary","api","system","platform","adapter",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":39},"01M6GV6FK50JQ7XPFA0EVCFDBJ","elegy-obsidian","Read, write, and search a local Obsidian vault via the official Obsidian Desktop CLI (v1.12.7+). Non-authoritative convenience layer; durable planning state continues to flow through elegy-planning and SQLite. User-invoked; do not auto-load.","https:\u002F\u002Fgithub.com\u002FSofreshx\u002FElegy\u002Fblob\u002Fmain\u002Fskills\u002Felegy-obsidian\u002FSKILL.md",[],[122,123,124,125,126,127,128,129,130,25,131,132,133,134,135,136,137,138,139,140],"elegy obsidian","obsidian","do","planning","official","load","mirror","true","tags","state","search","vault","auto","obsidian vault","sqlite","tasks","notes","cli","desktop",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":39},"01M6GV61N0F34CMFA7F4AT7C2D","elegy-doc-practices","Use when an agent or contributor needs to classify, place, scaffold, or validate documentation in the Elegy ecosystem — the central doctrine for ADRs, specs, guides, notes, and roadmap material across Elegy and downstream repos.","https:\u002F\u002Fgithub.com\u002FSofreshx\u002FElegy\u002Fblob\u002Fmain\u002Fskills\u002Felegy-doc-practices\u002FSKILL.md",[],[148,149,150,151,152,153,154,92,155,28,138,156,157,158,159],"doc","elegy doc practices","across","ecosystem","guides","material","classify","roadmap","documentation","scaffold","repos","validate",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":170,"publishedAt":39},"01M6GV5RR6R3XF7Q1EP9QZ4GVK","test-skill","A test skill for the app-binding fixture.","https:\u002F\u002Fgithub.com\u002FSofreshx\u002FElegy\u002Fblob\u002Fmain\u002Fshared\u002Fplugin-sdk\u002Ftests\u002Ffixtures\u002Fapp-binding-plugin\u002Fskills\u002Ftest-skill\u002FSKILL.md",[166,169],{"categoryNo":167,"categoryName":168,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[171,172,173,174,175],"Test Skill","test","app","fixture","binding",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":182,"publishedAt":39},"01M6GV59H2X6CJAYJCX7S4ERJE","elegy-planning","Use when an agent needs to create, inspect, update, validate, or export durable planning state — goals, roadmaps, plans, work points, todos, issues, review points, insights, and project runs — through the dedicated elegy-planning CLI over SQLite.","https:\u002F\u002Fgithub.com\u002FSofreshx\u002FElegy\u002Fblob\u002Fmain\u002Fplugins\u002Fplanning\u002Fskills\u002Felegy-planning\u002FSKILL.md",[],[183,125,28,184,185,186,187,188,189,21,136,190,131,191,34,159,139,29],"elegy planning","inspect","insights","plans","project","goals","export","issues","update"]