[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MDRYWH5BXVQ99ZHH0TCX7H":3,"skill-same:01M6MDRYWH5BXVQ99ZHH0TCX7H":86},{"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":28,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M6MDRYWH5BXVQ99ZHH0TCX7H","graymatter-analytics",null,"Use when GrayMatter should support analytics work by retrieving durable context, checking retrieval receipts, loading the live api-docs schema, and helping create user\u002Fworkspace-specific semantic layers without assuming tenant business objects exist.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FValkyrLabs\u002FGrayMatter\u002Fskills\u002Fgraymatter-analytics\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"analytics","graymatter analytics","graymatter","schema","when","tenant","layers","loading","api-docs","retrieval","live","objects","docs","use","business","user","work","workspace","receipts","api","create","support","2026-11-10 10:12:30",false,"---\nname: graymatter-analytics\ndescription: Use when GrayMatter should support analytics work by retrieving durable context, checking retrieval receipts, loading the live api-docs schema, and helping create user\u002Fworkspace-specific semantic layers without assuming tenant business objects exist.\n---\n\n# GrayMatter Analytics\n\nUse this skill when a user wants analytics, KPI, report, dashboard, or semantic-context work to use GrayMatter as the product surface for memory, retrieval, receipts, and live schema awareness.\n\n## Core Rule\n\n`\u002Fv1\u002Fapi-docs` is the source of truth for the current RBAC-visible schema.\n\nGrayMatter helpers may expect GrayMatter product surfaces such as memory, retrieval, receipts, status, and schema introspection when the plugin is installed and authenticated. They must not assume business objects such as `Invoice`, `UserPreference`, `StrategicPriority`, `KeyMetric`, `Customer`, `Workflow`, or `Application` exist until the current `\u002Fv1\u002Fapi-docs` says they exist for this account.\n\n## Start Here\n\n1. Ensure GrayMatter is activated or at least check status with the available GrayMatter tool or script.\n2. Retrieve relevant durable context through GrayMatter memory or retrieval receipts.\n3. Load or refresh `\u002Fv1\u002Fapi-docs` before using business objects, fields, relationships, or actions.\n4. Map the user question to only the object families and paths present in the live schema.\n5. If schema or retrieval evidence is missing, stale, partial, or conflicting, say so and ask for the smallest useful fallback.\n\n## Source Order\n\n1. Live `\u002Fv1\u002Fapi-docs` for schema, paths, components, fields, relationships, and actions.\n2. GrayMatter retrieval receipt for memory-backed answers, including its answer policy and coverage status.\n3. Live GrayMatter memory read\u002Fquery when receipts are unavailable.\n4. User-provided sources such as SQL, dashboards, docs, exports, screenshots, repository files, or local semantic layers.\n5. Local fallback files only when GrayMatter is unavailable or the user explicitly wants local-only work.\n\n## Business Object Rules\n\n- Treat object families outside the GrayMatter core as conditional.\n- Verify both the path\u002Fcomponent and the specific field or relationship before using it in analysis.\n- When an expected object family is missing, use the closest live schema object only if it is semantically appropriate and say why.\n- Do not synthesize unavailable schema objects from examples, docs, memories, or another user's tenant.\n- For high-stakes analytics, refresh schema and retrieve source evidence during the workflow, even when saved context exists.\n\n## Normalized Context Rules\n\nAnalytics quality depends on graph traversal, filters, and retrieval receipts seeing structured fields rather than blobs.\n\n- Do not write analytics context by stuffing metadata into `MemoryEntry.text` or `ContentData.contentData`.\n- Use `MemoryEntry.text` only for the concise durable fact, decision, todo, preference, handoff, or artifact summary.\n- Use `sourceChannel`, `metadata`, tags, and explicit relationships for scope, provenance, workspace, workflow, dashboard, artifact, and agent identifiers.\n- Use `ContentData` only for content artifacts or overflow detail; set or preserve `contentType`, `category`, `status`, `tags`, and JSON `metadata`.\n- Never send audit fields such as `ownerId`, `ownerID`, `createdDate`, `lastModifiedDate`, or `lastAccessedDate` in create\u002Fupdate payloads.\n- Before creating or updating a non-memory object, confirm the object and fields exist in `\u002Fv1\u002Fapi-docs`; prefer the first-class business object over a generic memory or content record.\n- When answering from memory or semantic retrieval, prefer retrieval receipts and respect their coverage, freshness, confidence, provenance, and answer policy.\n\n## Semantic Layers\n\nGrayMatter can help create workspace-specific semantic layers, but shared plugin skills must stay generic.\n\nUse `references\u002Fsemantic-layer-template.md` when a user wants reusable analytics context. The layer should be generated from that user's live schema and supplied sources, then stored in the user's workspace or skill directory. Do not ship customer-specific metrics, private MemoryEntry content, local absolute paths, or workspace decisions as a universal GrayMatter layer.\n\n## Answering Rules\n\n- Obey retrieval receipt policies such as retry, clarify, deny, low confidence, stale context, partial coverage, or conflicting context.\n- Keep raw credentials, tokens, private personal fields, row-level customer data, and long private memory bodies out of generated artifacts.\n- Separate product capability from tenant availability: GrayMatter may support schema-aware analytics, but the current tenant's `\u002Fv1\u002Fapi-docs` decides what can be analyzed.\n- Prefer precise source gaps over confident guesses.\n","# GrayMatter Analytics\n\nUse this skill when a user wants analytics, KPI, report, dashboard, or semantic-context work to use GrayMatter as the product surface for memory, retrieval, receipts, and live schema awareness.\n\n## Core Rule\n\n`\u002Fv1\u002Fapi-docs` is the source of truth for the current RBAC-visible schema.\n\nGrayMatter helpers may expect GrayMatter product surfaces such as memory, retrieval, receipts, status, and schema introspection when the plugin is installed and authenticated. They must not assume business objects such as `Invoice`, `UserPreference`, `StrategicPriority`, `KeyMetric`, `Customer`, `Workflow`, or `Application` exist until the current `\u002Fv1\u002Fapi-docs` says they exist for this account.\n\n## Start Here\n\n1. Ensure GrayMatter is activated or at least check status with the available GrayMatter tool or script.\n2. Retrieve relevant durable context through GrayMatter memory or retrieval receipts.\n3. Load or refresh `\u002Fv1\u002Fapi-docs` before using business objects, fields, relationships, or actions.\n4. Map the user question to only the object families and paths present in the live schema.\n5. If schema or retrieval evidence is missing, stale, partial, or conflicting, say so and ask for the smallest useful fallback.\n\n## Source Order\n\n1. Live `\u002Fv1\u002Fapi-docs` for schema, paths, components, fields, relationships, and actions.\n2. GrayMatter retrieval receipt for memory-backed answers, including its answer policy and coverage status.\n3. Live GrayMatter memory read\u002Fquery when receipts are unavailable.\n4. User-provided sources such as SQL, dashboards, docs, exports, screenshots, repository files, or local semantic layers.\n5. Local fallback files only when GrayMatter is unavailable or the user explicitly wants local-only work.\n\n## Business Object Rules\n\n- Treat object families outside the GrayMatter core as conditional.\n- Verify both the path\u002Fcomponent and the specific field or relationship before using it in analysis.\n- When an expected object family is missing, use the closest live schema object only if it is semantically appropriate and say why.\n- Do not synthesize unavailable schema objects from examples, docs, memories, or another user's tenant.\n- For high-stakes analytics, refresh schema and retrieve source evidence during the workflow, even when saved context exists.\n\n## Normalized Context Rules\n\nAnalytics quality depends on graph traversal, filters, and retrieval receipts seeing structured fields rather than blobs.\n\n- Do not write analytics context by stuffing metadata into `MemoryEntry.text` or `ContentData.contentData`.\n- Use `MemoryEntry.text` only for the concise durable fact, decision, todo, preference, handoff, or artifact summary.\n- Use `sourceChannel`, `metadata`, tags, and explicit relationships for scope, provenance, workspace, workflow, dashboard, artifact, and agent identifiers.\n- Use `ContentData` only for content artifacts or overflow detail; set or preserve `contentType`, `category`, `status`, `tags`, and JSON `metadata`.\n- Never send audit fields such as `ownerId`, `ownerID`, `createdDate`, `lastModifiedDate`, or `lastAccessedDate` in create\u002Fupdate payloads.\n- Before creating or updating a non-memory object, confirm the object and fields exist in `\u002Fv1\u002Fapi-docs`; prefer the first-class business object over a generic memory or content record.\n- When answering from memory or semantic retrieval, prefer retrieval receipts and respect their coverage, freshness, confidence, provenance, and answer policy.\n\n## Semantic Layers\n\nGrayMatter can help create workspace-specific semantic layers, but shared plugin skills must stay generic.\n\nUse `references\u002Fsemantic-layer-template.md` when a user wants reusable analytics context. The layer should be generated from that user's live schema and supplied sources, then stored in the user's workspace or skill directory. Do not ship customer-specific metrics, private MemoryEntry content, local absolute paths, or workspace decisions as a universal GrayMatter layer.\n\n## Answering Rules\n\n- Obey retrieval receipt policies such as retry, clarify, deny, low confidence, stale context, partial coverage, or conflicting context.\n- Keep raw credentials, tokens, private personal fields, row-level customer data, and long private memory bodies out of generated artifacts.\n- Separate product capability from tenant availability: GrayMatter may support schema-aware analytics, but the current tenant's `\u002Fv1\u002Fapi-docs` decides what can be analyzed.\n- Prefer precise source gaps over confident guesses.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FValkyrLabs\u002FGrayMatter\u002Fskills\u002Fgraymatter-analytics",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill graymatter-analytics",{"tool":72,"command":73},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill graymatter-analytics",{"tool":75,"command":76},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill graymatter-analytics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FValkyrLabs\u002FGrayMatter\u002Fskills\u002Fgraymatter-analytics\u002FSKILL.md",true,[80],{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fsemantic-layer-template.md","REFERENCE","参考文档",3516,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FValkyrLabs\u002FGrayMatter\u002Fskills\u002Fgraymatter-analytics\u002Freferences\u002Fsemantic-layer-template.md",[87,97,105,113,121,129],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":91,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":96},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":91,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":96},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":91,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":96},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"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":91,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":96},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":91,"licenseFileUrl":125,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":96},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":91,"licenseFileUrl":133,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":96},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]