[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B7VQ4EC4H4VTMWPXXPC5WH":3,"skill-same:01M7B7VQ4EC4H4VTMWPXXPC5WH":93},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7B7VQ4EC4H4VTMWPXXPC5WH","ac-audit-logging",null,"Building logs that serve as evidence rather than telemetry: what events an audit trail must record and who its reader is, tamper-evidence through hash chaining and external anchoring, append-only storage and the deletion problem, query patterns for investigators, retention and privacy tension with the trail's purpose, structured event schema for auditability, and the written audit record. It explains how to make a log that can be trusted after the fact; it never recommends a log product and never claims tamper-proof, only tamper-evident. Use when asking \"audit log\", \"tamper evident\", \"hash chain log\", \"append only log\", \"who changed this record\", \"immutable log\", \"audit trail design\", \"compliance evidence\", \"log integrity\", \"sequence number gap\". Not for observability and SLO telemetry (ac-reliability), not for structured logging in general (ac-reliability), not for access control decisions themselves (ac-security-engineer).","jiayaoqijia\u002Fcryptoskill","jiayaoqijia","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1453879?v=4","01M6GMYTX7Q7S504VC6E756ENR","YQ","01M6GMYV1QKJ1CC75MTTGT9PR0",81,"MIT","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-audit-logging\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-audit-logging\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ac-audit-logging\ndescription: \"Building logs that serve as evidence rather than telemetry: what events an audit trail must record and who its reader is, tamper-evidence through hash chaining and external anchoring, append-only storage and the deletion problem, query patterns for investigators, retention and privacy tension with the trail's purpose, structured event schema for auditability, and the written audit record. It explains how to make a log that can be trusted after the fact; it never recommends a log product and never claims tamper-proof, only tamper-evident. Use when asking \\\"audit log\\\", \\\"tamper evident\\\", \\\"hash chain log\\\", \\\"append only log\\\", \\\"who changed this record\\\", \\\"immutable log\\\", \\\"audit trail design\\\", \\\"compliance evidence\\\", \\\"log integrity\\\", \\\"sequence number gap\\\". Not for observability and SLO telemetry (ac-reliability), not for structured logging in general (ac-reliability), not for access control decisions themselves (ac-security-engineer).\"\nlicense: MIT\nmetadata:\n  domain: software-engineering\nstatus: seedling\n---\n\n# Audit logging\n\n## Overview\n\nAn audit log is a different object from a telemetry log. Telemetry answers \"how is the system behaving\"; an audit trail answers \"who did what, when, and what was the state before\" — and its reader is not an engineer at a dashboard but an investigator, an auditor, or a court, months later, possibly hostile to the system's operators. Everything about its design follows from that reader.\n\nThe central property is integrity: a trail that can be edited after the fact is not evidence, and the honest engineering term is tamper-evident, not tamper-proof. Hash chaining makes local edits detectable; anchoring the chain's head somewhere the system cannot reach makes even a full rewrite visible. The second property is completeness — the absence of an expected event is itself a finding, which means sequence gaps must be visible rather than smoothed over.\n\nPrimary sources: \u003Chttps:\u002F\u002Fcsrc.nist.gov\u002Fpubs\u002Fsp\u002F800\u002F92\u002Ffinal> and \u003Chttps:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc6962.html>.\n\n## When to use\n\n- When a system must answer who changed what, and when.\n- When a compliance or regulatory regime requires evidence-grade records.\n- When log integrity must survive a compromised host.\n- When designing what an investigator can query, years later.\n\n## When NOT to use\n\n- For operational telemetry and SLO metrics (use ac-reliability).\n- For application logging in general (use ac-reliability).\n- For authorization and access-control rules (use ac-security-engineer).\n\n## Subskill Index\n\n| Leaf | Domain segment | Scope (one line) |\n|---|---|---|\n| `subskills\u002Fwhat-to-record.md` | `software-engineering\u002Fwhat-to-record` | The event set, the actor identity problem, and the before-and-after state. |\n| `subskills\u002Fhash-chaining-and-anchoring.md` | `software-engineering\u002Fhash-chaining-and-anchoring` | Chain each entry to its predecessor and anchor the head off-host. |\n| `subskills\u002Fappend-only-storage.md` | `software-engineering\u002Fappend-only-storage` | Write-once storage, the deletion problem, and who can rotate. |\n| `subskills\u002Fsequence-and-gaps.md` | `software-engineering\u002Fsequence-and-gaps` | Sequence numbers, visible gaps, and the silence they can indicate. |\n| `subskills\u002Finvestigator-queries.md` | `software-engineering\u002Finvestigator-queries` | Answering who-changed-what-when without a forensic project. |\n| `subskills\u002Fretention-and-privacy.md` | `software-engineering\u002Fretention-and-privacy` | Retention law, personal data in the trail, and redaction without rewriting. |\n| `subskills\u002Faudit-record.md` | `software-engineering\u002Faudit-record` | The written audit record: event set, chain, storage, and verification. |\n\n## Status and honest limits\n\nAudit trails are governed by rules that vary by jurisdiction and regime, and this skill designs the engineering object, not the compliance opinion — whether a given trail satisfies a given regulation is a question for the accountable officer. The integrity mechanisms here detect alteration; they do not prevent a sufficiently privileged attacker from stopping the logger entirely, which is why the record treats silence as a signal, not an absence of news.\n","# Audit logging\n\n## Overview\n\nAn audit log is a different object from a telemetry log. Telemetry answers \"how is the system behaving\"; an audit trail answers \"who did what, when, and what was the state before\" — and its reader is not an engineer at a dashboard but an investigator, an auditor, or a court, months later, possibly hostile to the system's operators. Everything about its design follows from that reader.\n\nThe central property is integrity: a trail that can be edited after the fact is not evidence, and the honest engineering term is tamper-evident, not tamper-proof. Hash chaining makes local edits detectable; anchoring the chain's head somewhere the system cannot reach makes even a full rewrite visible. The second property is completeness — the absence of an expected event is itself a finding, which means sequence gaps must be visible rather than smoothed over.\n\nPrimary sources: \u003Chttps:\u002F\u002Fcsrc.nist.gov\u002Fpubs\u002Fsp\u002F800\u002F92\u002Ffinal> and \u003Chttps:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc6962.html>.\n\n## When to use\n\n- When a system must answer who changed what, and when.\n- When a compliance or regulatory regime requires evidence-grade records.\n- When log integrity must survive a compromised host.\n- When designing what an investigator can query, years later.\n\n## When NOT to use\n\n- For operational telemetry and SLO metrics (use ac-reliability).\n- For application logging in general (use ac-reliability).\n- For authorization and access-control rules (use ac-security-engineer).\n\n## Subskill Index\n\n| Leaf | Domain segment | Scope (one line) |\n|---|---|---|\n| `subskills\u002Fwhat-to-record.md` | `software-engineering\u002Fwhat-to-record` | The event set, the actor identity problem, and the before-and-after state. |\n| `subskills\u002Fhash-chaining-and-anchoring.md` | `software-engineering\u002Fhash-chaining-and-anchoring` | Chain each entry to its predecessor and anchor the head off-host. |\n| `subskills\u002Fappend-only-storage.md` | `software-engineering\u002Fappend-only-storage` | Write-once storage, the deletion problem, and who can rotate. |\n| `subskills\u002Fsequence-and-gaps.md` | `software-engineering\u002Fsequence-and-gaps` | Sequence numbers, visible gaps, and the silence they can indicate. |\n| `subskills\u002Finvestigator-queries.md` | `software-engineering\u002Finvestigator-queries` | Answering who-changed-what-when without a forensic project. |\n| `subskills\u002Fretention-and-privacy.md` | `software-engineering\u002Fretention-and-privacy` | Retention law, personal data in the trail, and redaction without rewriting. |\n| `subskills\u002Faudit-record.md` | `software-engineering\u002Faudit-record` | The written audit record: event set, chain, storage, and verification. |\n\n## Status and honest limits\n\nAudit trails are governed by rules that vary by jurisdiction and regime, and this skill designs the engineering object, not the compliance opinion — whether a given trail satisfies a given regulation is a question for the accountable officer. The integrity mechanisms here detect alteration; they do not prevent a sufficiently privileged attacker from stopping the logger entirely, which is why the record treats silence as a signal, not an absence of news.\n",{"name":5,"status":25,"license":15,"metadata":26,"description":7},"seedling",{"domain":27},"software-engineering","main","4aff87e77e63c1886a978b82902814d015f55a4f","skills\u002Fexchanges\u002Fanoscranel-ac-audit-logging",17,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia","https:\u002F\u002Feth2030.com","Hardcore infra. Building @alt-research and applied cryptography.","2026-11-15 02:28:10",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add jiayaoqijia\u002Fcryptoskill --skill ac-audit-logging",{"tool":43,"command":44},"bunx","bunx skills add jiayaoqijia\u002Fcryptoskill --skill ac-audit-logging",{"tool":46,"command":47},"pnpm","pnpm dlx skills add jiayaoqijia\u002Fcryptoskill --skill ac-audit-logging","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-audit-logging\u002FSKILL.md",true,[51,55,61,65,69,73,77,81,85,89],{"path":52,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":16},"LICENSE","许可证",1068,{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"SOURCE.md","REFERENCE","参考文档",372,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-audit-logging\u002FSOURCE.md",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"subskills\u002Fappend-only-storage.md",3219,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-audit-logging\u002Fsubskills\u002Fappend-only-storage.md",{"path":66,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":67,"sourceHtmlUrl":68},"subskills\u002Faudit-record.md",3359,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-audit-logging\u002Fsubskills\u002Faudit-record.md",{"path":70,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":71,"sourceHtmlUrl":72},"subskills\u002Fhash-chaining-and-anchoring.md",3295,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-audit-logging\u002Fsubskills\u002Fhash-chaining-and-anchoring.md",{"path":74,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":75,"sourceHtmlUrl":76},"subskills\u002Finvestigator-queries.md",3067,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-audit-logging\u002Fsubskills\u002Finvestigator-queries.md",{"path":78,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":79,"sourceHtmlUrl":80},"subskills\u002Fretention-and-privacy.md",3268,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-audit-logging\u002Fsubskills\u002Fretention-and-privacy.md",{"path":82,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":83,"sourceHtmlUrl":84},"subskills\u002Fsequence-and-gaps.md",3116,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-audit-logging\u002Fsubskills\u002Fsequence-and-gaps.md",{"path":86,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":87,"sourceHtmlUrl":88},"subskills\u002Fwhat-to-record.md",3045,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-audit-logging\u002Fsubskills\u002Fwhat-to-record.md",{"path":90,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":91,"sourceHtmlUrl":92},"TRUST.auto.yaml",2217,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-audit-logging\u002FTRUST.auto.yaml",[94,102,110,118,126,134],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":20},"01M7DTKCERMV0RNX3HZJP4CZ26","troves","Deposit and withdraw from Troves DeFi yield vault strategies on Starknet. View available strategies, check positions, and manage vault deposits. Use this skill when the user mentions Troves, vault, yield vault, DeFi vault, strategy, yield farming, vault deposit, vault withdraw, earning yield through vaults, passive yield strategies, or wants to deposit into or withdraw from a yield strategy — even if they don't say \"Troves\" explicitly.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-troves\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-troves\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":20},"01M7DTK6CJSMGC8KCQHGNYFZBD","trade","Swap tokens on Starknet via Fibrous DEX aggregator. Supports per-provider selection (avnu, ekubo, or auto to race all). Use this skill when the user wants to swap, exchange, trade, convert, buy, or sell one token for another on Starknet. Also use when the user asks about token prices, exchange rates, DEX routing, best swap route, or wants to check how much they would receive for a given amount — even if they don't explicitly say \"swap\".","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-trade\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-trade\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":20},"01M7DTJZ6A0X4PAW3Y8W4J9K64","staking","Stake, unstake, claim, and compound rewards for STRK, WBTC, tBTC, SolvBTC, and LBTC on Starknet. View validators, pools, and staking positions. Use this skill when the user mentions staking, delegating, validators, staking pools, rewards, compounding, unstaking, earning yield, passive income on crypto, or wants to earn on their STRK or BTC tokens — even if they don't say \"stake\" explicitly.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-staking\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-staking\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":122,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":20},"01M7DTJSDZJKCDMW7GHRF4BRH5","send","Send STRK, ETH, or any ERC-20 token to a Starknet address. Supports simulation (dry-run) before execution. Use this skill when the user wants to send, transfer, pay, tip, or move tokens to another wallet address on Starknet. Also trigger when the user mentions sending funds to someone, making a payment, transferring assets, or moving crypto to a specific address — even if they just say \"pay 10 STRK to 0x...\".","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-send\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-send\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":130,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":20},"01M7DTJG1E480D51ZQ7WKDQ26K","portfolio","View a comprehensive DeFi portfolio dashboard and optimize portfolio allocation via automated rebalancing. Use this skill when the user wants an overview, summary, dashboard, total value, net worth, portfolio rebalancing, target allocation, or wants to see all their DeFi positions across Starknet at once. Also trigger when the user asks \"what do I have\", \"show me everything\", \"how much am I worth\", \"my positions\", \"my investments\", \"rebalance my portfolio\", \"I want 50% ETH\", \"optimize my holdings\", or any request for a holistic view of their Starknet holdings — even if they don't explicitly say \"portfolio\".","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-portfolio\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-portfolio\u002FSKILL.md",[],[],{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":138,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":20},"01M7DTJ7M8TE9R2N36HFBZDGVD","multi-swap","Execute multiple token swaps in a single Starknet transaction via Fibrous (default). Supports per-provider selection (avnu, ekubo, or auto to race all). Supports 2-3 swap pairs bundled into one multicall. Use this skill when the user wants to swap multiple token pairs at once, do batch swaps, execute several trades simultaneously, perform parallel swaps, or do bulk trading in one transaction. Also trigger when the user mentions \"two swaps\", \"three swaps\", \"swap X and Y at the same time\", or wants to convert multiple tokens in a single call.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-multi-swap\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-multi-swap\u002FSKILL.md",[],[]]