[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6M95Q5E0TYTXHY3MFKH32FP":3,"skill-same:01M6M95Q5E0TYTXHY3MFKH32FP":133},{"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":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":62,"ownerHtmlUrl":63,"ownerBlogUrl":64,"ownerDescription":65,"updatedAt":66,"install":67,"resources":80},"01M6M95Q5E0TYTXHY3MFKH32FP","suede-code",null,"Use when explicitly asked \"review this PR\" or to grade a diff, branch, or commit range. Suede AI returns evidence-backed P0-P3 findings, fix paths and an A-F ship grade; supports findings-only, grade-only and fix modes, seven review lanes, security checks, deploy safety and commit dirt. NOT FOR: automatic CI enforcement (use suede-ci-gate), agent evaluations (use suede-ai-eval), implementation-plan search (use suede-graph-flo-xr), or parallel fix coordination (use suede-agent-teams).","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\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-code\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"suede code","code","coordination","when","automatic","agent-teams","paths","only","fix","eval","branch","returns","review","plan","ship","Safety","ci","graph","search","commit","security","2026-11-10 10:12:30",false,"---\nname: suede-code\ndescription: \"Use when explicitly asked \\\"review this PR\\\" or to grade a diff, branch, or commit range. Suede AI returns evidence-backed P0-P3 findings, fix paths and an A-F ship grade; supports findings-only, grade-only and fix modes, seven review lanes, security checks, deploy safety and commit dirt. NOT FOR: automatic CI enforcement (use suede-ci-gate), agent evaluations (use suede-ai-eval), implementation-plan search (use suede-graph-flo-xr), or parallel fix coordination (use suede-agent-teams).\"\nmetadata:\n  display-name: \"Suede AI Code Skills\"\n---\n\n# Suede AI Code Skills\n\nOne skill for judging code: what is wrong, and whether it ships. Every finding\nhas a file, evidence, and a fix path. Every grade has the evidence that earned\nit. No finding without evidence; no volume without signal.\n\n**Runs only when asked.** Never fire this as a side effect of a diff, a save,\nor a commit.\n\n## Compatibility\n\nAn agent with repository read access and Git; Bash is needed for local tests and the bundled commit-dirt scan. Fix mode additionally needs authorized file edits. Review can proceed with explicitly unverified runtime checks when execution is unavailable.\n\n## Gate policy: advisory, not blocking\n\nEvery check, grade, and ship verdict here is a recommendation to the user, not\na control on the agent.\n\n- Run every check and report results honestly. `ship`, `ship-with-caveats`,\n  `hold`, letter grades, and BLOCKED items are advice attached to the work.\n- Never block, delay, skip, or rewrite the action the user asked for because a\n  gate said hold. A failed gate changes what you report, never what you do.\n- Single exception: an extreme-risk finding (data loss, credential exposure,\n  legal or rights violation, payment mistake, irreversible public damage).\n  Pause, state the risk and the options, and let the user pick. Their choice\n  is final.\n\n## Pick the mode\n\n| Request sounds like | Mode | Emits |\n|---|---|---|\n| \"review and grade\", \"is this safe to ship\", \"check this PR\" | **full** (default) | Findings, grade, deploy safety, commit dirt, ship gate |\n| \"findings only\", \"no grade\", \"line by line\", \"find the bugs\" | **`--findings-only`** | Findings, deploy safety, commit dirt, ship gate. No letters. |\n| \"grade only\", \"give it a letter\", \"A-F verdict\", \"should this merge\" | **`--grade-only`** | Lane grades, caps, required upgrades, ship gate. No findings list. |\n\nGrade-only still runs Step 1 (Instant-F) and still reads the code. It skips\nthe itemized findings output, not the investigation.\n\nOther modes that combine with any of the above:\n\n- **Plan review:** nothing built yet; check scope, sequencing, acceptance\n  criteria, test mapping, and missing decisions.\n- **Fix verification:** after fixes, rescan only the changed files and confirm\n  each original finding is gone.\n- **Release review:** add build, secrets, env, public copy, screenshots,\n  metadata, and live or API readback.\n- **`--fix`:** apply fixes (see Fix Mode).\n- **`--threat-verify`:** confirm declared threat-model mitigations exist.\n  Procedure in `references\u002Fthreat-verify.md`; read it only in this mode.\n\n**Depth** (state it at the top of every output):\n\n- `--quick` (about 2 min): pattern scan for obvious bugs, secrets, missing null\n  checks, injection, broken error handling. No cross-file analysis.\n- `--standard` (default, about 10 min): per-file correctness on changed paths,\n  language traps, state handling, test coverage of changed behavior, call graph\n  within changed files, maintainability baseline.\n- `--deep` (about 25 min): full import graph, call-chain tracing, whole-repo and\n  history pass, critic lanes. Use for auth, payments, migrations, public APIs.\n\nModel: Sonnet by default. Recommend Opus for auth, payments, and public API\nsurfaces.\n\n## Pre-flight\n\nName three things before analysis:\n\n- **Target:** repo, branch, PR, commit range, diff, route, API, or release build.\n- **Intent:** what the change claims to do. Find the spec in this order: issue\n  references in commits and PR body (`#123`, `Closes #45`), a path the caller\n  passed, a matching file under `docs\u002F` or `specs\u002F`. If none exists, write\n  \"no spec available\" and judge intent from the PR description alone. Never\n  invent requirements.\n- **Risk lanes:** frontend, backend, data, auth, payments, contracts, iOS,\n  release, public copy, analytics, secrets, deployment, docs.\n\nPin the comparison point and prove it is reviewable: `git rev-parse \u003Cbase>`\nresolves, diff with three dots (`git diff \u003Cbase>...HEAD`) so the comparison\nruns against the merge-base, and the diff is non-empty. A bad ref or empty\ndiff fails here in one line.\n\n## Context graph\n\nBuild it before judging the diff:\n\n1. Changed files and generated files.\n2. Imports, callers, routes, handlers, jobs, hooks, models, schemas, and\n   config or env dependencies the change touches.\n3. Tests, fixtures, migrations, release scripts, docs, and screenshots that\n   should move with the behavior.\n4. Runtime surfaces: local route, live URL, API endpoint, simulator flow,\n   dashboard, store metadata, deploy target.\n5. Domain contracts: ownership, rights and provenance, payments and wallets,\n   agent commerce, and published-statement accuracy.\n\nFlag beyond-the-diff risk when related files, defaults, docs, env, or deploy\nrequirements no longer agree.\n\n## Run the repo's own gates first\n\nDo not hand-review what a tool already decides. Detect what the repo ships\n(`package.json` scripts, config files, lockfiles) and run only that. Never add\na tool the repo does not use. Never report a result you did not run.\n\n| Stack | Type check | Lint | Test | Other |\n|---|---|---|---|---|\n| Web \u002F Node | `npx tsc --noEmit` | `npm run lint` (changed files) | `npm test` | `npm audit` when deps changed |\n| MCP server (Node) | `node --check \u003Cserver>.mjs` | configured linter | repo MCP tests | One stdio session: `initialize`, `notifications\u002Finitialized`, then list\u002Fcall\u002Fread\u002Fget |\n| iOS \u002F Swift | the build is the check | SwiftLint if configured | XCTest target | `xcodebuild -scheme X -destination 'platform=iOS Simulator,name=\u003Cdevice>' build` |\n| API \u002F backend | compile step if any | configured linter | contract or schema tests | OpenAPI validation against the live route |\n\nSeverity mapping: a type error on a changed line is P2 (P1 on a critical\npath); a failing test on changed behavior is P1; a test that silently stopped\nrunning is P2; a reachable, exploitable dependency CVE is P0 or P1; a verified\nlive secret is P0; a broken production build in a release review is P0.\n\nCite command, exit status, and the file:line it implicates. A gate that cannot\nrun goes in Verification as \"not run\" with the reason.\n\n**House rules bind.** Read `CLAUDE.md`, `AGENTS.md`, `CONTRIBUTING.md`,\n`.editorconfig`, and formatter, linter, or review config. Do not flag what a\nrule permits; do flag what it forbids. The nearest-ancestor rule wins for files\nunder its path. When the user dismisses a finding as deliberate, record it in\none line (pattern, why allowed, path scope) and do not raise it again.\n\n## Step 1: Instant-F triggers (always first, every mode)\n\nAny match is an automatic **F** and a P0 finding. Report file and line. Other\nlanes cannot raise the grade.\n\n- **Secrets:** hardcoded API key, token, or password in committed source; a\n  committed private key or certificate; a signing secret outside a secret\n  manager.\n- **Injection:** SQL built by string concatenation with user input; shell\n  command from user input via exec, spawn, or eval; unescaped user input\n  rendered where XSS is reachable.\n- **Auth bypass:** middleware with a skip path (early return, swallowed\n  exception, always-true condition); a permission check a request param can\n  bypass; JWT accepting `alg: none` or a hardcoded secret.\n- **Payments and wallets:** a handler that swallows errors; a webhook with no\n  signature verification; amount or recipient taken from untrusted input\n  without server-side validation.\n- **Data destruction:** a DROP or destructive ALTER with no rollback and no\n  tested restore; bulk delete or update with no WHERE or a user-controlled\n  WHERE; production cache wipes with no restore path.\n- **Plaintext sensitive data:** passwords stored or logged in plaintext; PII\n  sent to unencrypted logs or analytics; card, SSN, or health data in an\n  unencrypted field.\n\n## Step 2: Language and platform traps\n\nLoad only the sections that match the diff:\n\n- `references\u002Ftraps-web.md`: TypeScript, React, accessibility, Next.js, SEO\n  impact, database (Drizzle, Prisma), performance and Core Web Vitals.\n- `references\u002Ftraps-swift-ios.md`: Swift, SwiftUI, and client-server contract\n  drift for iOS.\n- `references\u002Fmaintainability-baseline.md`: twelve structural checks for\n  `--standard` and `--deep`, diff-scoped and always labeled as judgment.\n\n## Step 3: Security baseline\n\nRuns automatically when the diff touches `auth\u002F`, `api\u002F`, `middleware\u002F`,\n`routes\u002F`, `pages\u002Fapi\u002F`, or imports crypto, session, or payment modules. Cite\nthe category in each finding using the **OWASP Top 10:2025** numbering: A01\nBroken Access Control (now includes SSRF), A02 Security Misconfiguration, A03\nSoftware Supply Chain Failures, A04 Cryptographic Failures, A05 Injection, A06\nInsecure Design, A07 Authentication Failures, A08 Software or Data Integrity\nFailures, A09 Security Logging and Alerting Failures, A10 Mishandling of\nExceptional Conditions. API and mobile changes also map to the OWASP API\nSecurity Top 10 (2023) and MASVS. What counts as a finding per category is in\n`references\u002Fsecurity-baselines.md`.\n\n**Observability delta** (any new handler, endpoint, job, cron, or consumer):\nflag `catch` blocks that only `console.error` or swallow silently; new paths\nwith no log on entry or failure; React subtrees with no error boundary; new DB,\nexternal API, or model calls with no timing or trace span; analytics events\nthe old code fired and the new code dropped; background jobs that finish\nwithout logging count, duration, or failure reason.\n\n## Step 4: Deep pass (`--deep` only)\n\n- **Reverse dependencies:** find every caller of a changed function, type,\n  route, or constant across the repo. Name the call sites you checked.\n- **Shared assumptions:** for a changed schema, env var, default, or\n  invariant, find other places that assume the old value.\n- **History:** `git log -L` or `git blame` the touched lines. A change that\n  reintroduces a previously fixed shape is a regression; cite the prior commit.\n- **Sibling pattern:** compare to the nearest analog (other handlers, other\n  migrations). A lone handler skipping the shared auth wrapper is P1 even if\n  it works.\n- **Critic lanes** for auth, payments, migrations, or public APIs: a change\n  mapper, runtime critic, security critic, product critic, and test critic,\n  each reporting separately. Collect consensus. If a high-severity concern\n  survives a fix cycle, keep `hold` and name the smallest next check.\n\nA whole-repo claim with no named symbols is not evidence.\n\n## Step 5: Intent and scope\n\n- **Claim vs diff:** map each acceptance criterion to a code path or test.\n  Claimed behavior with no matching change is a P1 truth gap.\n- **Scope creep:** flag unrelated refactors, bundled dependency bumps, and\n  formatting sweeps that bury the change. Recommend a split.\n- **Effort signal:** state files and net lines changed and rate the review\n  effort: trivial, moderate, heavy, or too large to review safely.\n- **Walkthrough** (four or more files): a table of file, what changed, risk\n  lane. Add a mermaid `sequenceDiagram` or `flowchart` only when data crosses\n  three or more boundaries or an async, auth, or payment path changes.\n\n## Step 6: Grade (full and `--grade-only`)\n\nFor full and grade-only modes, read [the complete grading contract](references\u002Fgrading-contract.md) before assigning a grade. It defines all seven lanes, letter meanings, gate mapping, surface caps and debt weighting. An Instant-F or deploy-safety result still applies in every mode; never assign a letter from impression.\n\n## Step 7: Deploy safety (every mode, every run)\n\nRate each `pass | conditional | block`:\n\n- **Breaking changes:** a public API, schema, config key, or interface changes\n  with no versioned migration or fallback → block.\n- **Rollback safety:** `git revert` cannot undo it (migrations, sent email,\n  charges, deletes, storage writes, queue publishes) → block.\n- **Blast radius:** state it as `~0%` (flagged), `~partial` (one flow), or\n  `~100%` (shared middleware, auth, hot query).\n- **Environment readiness:** a required env var, secret, or flag is not in\n  production yet → block.\n- **Dependency changes:** new dependency with a known CVE, or unpinned in\n  production → block.\n- **Data mutations:** irreversible writes with no tested restore → block.\n- **Security delta:** improved, neutral, or new attack surface without\n  mitigation → block.\n- **Automation coverage:** no CI covering the changed surface, or required\n  checks not enforced on the default branch, in a production-connected repo →\n  block.\n\n## Step 8: Commit dirt (every mode, every run)\n\nRun the bundled scanner from the target repo instead of eyeballing:\n`bash \u003Cskill-dir>\u002Fscripts\u002Fcommit-dirt-scan.sh main...HEAD`, or pipe a diff\nwith `-`. It is read-only and always exits 0. Confirm each hit against the\ndiff before reporting. If it cannot run, check every added line by hand.\n\nSeven categories: secrets and credentials; debug artifacts; conflict markers;\nstaged build output (`node_modules\u002F`, `.next\u002F`, `dist\u002F`, `.DS_Store`, logs);\nWIP breadcrumbs (`DO NOT MERGE`, `TEMP:`, lorem ipsum); oversized or binary\nblobs over 500 KB; exposed internals (internal hosts, staging URLs, personal\nemails). Rate each `clean | suspicious | dirty`. Overall **DIRTY** is a P0\nfinding and moves the gate to `hold`. **SUSPICIOUS** is named for the reviewer\nto confirm.\n\n## Findings: format and precision\n\nLead with findings by severity. Group a repeated pattern once (\"appears in 4\nfiles: ...\"). If a structural defect exists, report it first and alone, and\nhold the line-level findings it governs as deferred.\n\nP0 and P1 use the full block:\n\n```\n[P0] path\u002Fto\u002Ffile.ts:142\nIssue: JWT secret falls back to empty string; any token is valid when SECRET is unset.\nFix: process.env.JWT_SECRET ?? (() => { throw new Error('JWT_SECRET required') })()\nVerify: set JWT_SECRET=\"\" and curl \u002Fapi\u002Fme: expect 401, currently 200.\nOWASP: A04:2025 Cryptographic Failures\nConfidence: high\n```\n\nP2 and P3 get one line each:\n\n```\n[P2] components\u002FFeed.tsx:88, index used as key on .map(); use item.id.\n```\n\n**Severity:** P0 data loss, security exposure, payment loss, broken release,\nor unsafe public behavior. P1 likely production regression, auth bug, broken\nprimary path, false published statement, missing deploy requirement. P2\nreal edge-case failure, incomplete state, test gap on changed behavior. P3\nlow-risk cleanup. A concern that cannot be tied to a file, route, command, or\nbehavior goes under Open Questions.\n\n**Confidence is observable:** `high` = reproduced, traced across the call\ngraph, or tied to a named failing input; `medium` = read, not executed;\n`low` = looks wrong, nothing proves it. Label every P0 and P1. A low-confidence\nsecurity suspicion keeps its severity with the label attached; low-confidence\nstyle notes collapse into one \"nitpicks\" line.\n\n**Before emitting, cut** anything with no file:line and fix, anything a gate\nalready reports, and anything that would not change the ship decision or earn\na human reviewer's comment.\n\n## Fix mode (`--fix` or an explicit request)\n\n1. Auto-apply local P2 and P3 fixes (single file, no contract change), one\n   commit per finding ID.\n2. Present P0 and P1 as fix briefs first: failing behavior and evidence, files\n   to open, expected change, acceptance criteria, verification command, WIP to\n   preserve. Never auto-apply to auth, payment, or migration code without\n   explicit confirmation.\n3. Re-run the relevant mode on changed files and mark each finding resolved or\n   escalated.\n4. Stop after 3 cycles on the same finding and escalate it as a design issue.\n\n## Suede-specific checks\n\nAuth and session behavior across app, API, native shells, and server ·\nrights, provenance, licensing, royalty, and agent-commerce claims match\nimplemented behavior · payment, wallet, x402, checkout, and credit flows fail\nclosed · public pages invent no metrics, pricing, partners, testimonials, or\nrelease promises · deploy and account assumptions match local guidance before\nproduction claims · store screenshots, metadata, and privacy answers match the\napp · migrations, env, flags, cron, queues, webhooks, and secrets are\ndocumented · contracts do not drift across web, backend, mobile, and docs.\n\n## Red flags: stop\n\n- \"CI is green, so it's fine.\" CI that never exercised the change is not\n  evidence.\n- \"The diff is small.\" Small diffs touch auth too. Step 1, 7, and 8 run every\n  time.\n- \"I wrote this, I know it works.\" Switch to review mode and hunt what your\n  implementation would miss.\n- \"The PR description explains it.\" Review the diff, not the story about it.\n- \"It was hard work, round up to B.\" Effort never moves a grade; evidence does.\n- \"Flag everything to be safe.\" Volume is noise. Run the precision cut.\n\n## Output\n\nOpen with **Simple explanation**: one plain paragraph a ten-year-old can follow\ncovering whether it passed and the single biggest reason. Then, by mode:\n\n```text\nDepth:\nFindings            (full, --findings-only)\nCode Grade          (full, --grade-only: 7 lanes + overall, cap applied, why, required upgrades)\nDeploy Safety       (all modes: 8 dimensions + SAFE TO DEPLOY | DEPLOY WITH CONDITIONS | DO NOT DEPLOY)\nCommit Dirt         (all modes: 7 categories + CLEAN | SUSPICIOUS | DIRTY)\nOpen Questions\nVerification        (checked \u002F not checked, with commands and exit codes)\nSHIP GATE: hold | ship-with-caveats | ship: [one sentence naming the blocker or caveat]\n```\n\nFor no findings, say so and name residual risk or unrun checks. To revise a\ngrade, name what changed. Silence means accepted.\n\nWorked examples, read only when calibrating: `references\u002Fworked-example.md`\n(a full pass on a real file) and `references\u002Fworked-example-grade-only.md`\n(lane arithmetic in grade-only mode).\n\n## Boundaries\n\n- Preserve user and other-agent WIP. Never stage, revert, or rewrite unrelated\n  files. Apply fixes only under Fix Mode.\n- Never invent tests, screenshots, live checks, deploy status, or gate results.\n- Never auto-apply fixes to auth, payment, or migration code without\n  confirmation.\n- A style choice no rule, formatter, or real cost governs is not a finding.\n\n## Routing\n\n- Make CI enforce the verdict on every merge → **suede-ci-gate**\n- The diff ships LLM, RAG, or agent behavior with no eval coverage →\n  **suede-ai-eval**\n- Several implementation plans need comparing before one multi-file change is\n  built → **suede-graph-flo-xr**\n- Fixes span several coordinated lanes → **suede-agent-teams**\n- The same value is stated on two surfaces that can drift →\n  **suede-parity-contract**\n\n## Worked contract\n\n[Worked contract](references\u002Fusage-contract.md) gives a bounded input, expected output and failure check for this workflow.\n","# Suede AI Code Skills\n\nOne skill for judging code: what is wrong, and whether it ships. Every finding\nhas a file, evidence, and a fix path. Every grade has the evidence that earned\nit. No finding without evidence; no volume without signal.\n\n**Runs only when asked.** Never fire this as a side effect of a diff, a save,\nor a commit.\n\n## Compatibility\n\nAn agent with repository read access and Git; Bash is needed for local tests and the bundled commit-dirt scan. Fix mode additionally needs authorized file edits. Review can proceed with explicitly unverified runtime checks when execution is unavailable.\n\n## Gate policy: advisory, not blocking\n\nEvery check, grade, and ship verdict here is a recommendation to the user, not\na control on the agent.\n\n- Run every check and report results honestly. `ship`, `ship-with-caveats`,\n  `hold`, letter grades, and BLOCKED items are advice attached to the work.\n- Never block, delay, skip, or rewrite the action the user asked for because a\n  gate said hold. A failed gate changes what you report, never what you do.\n- Single exception: an extreme-risk finding (data loss, credential exposure,\n  legal or rights violation, payment mistake, irreversible public damage).\n  Pause, state the risk and the options, and let the user pick. Their choice\n  is final.\n\n## Pick the mode\n\n| Request sounds like | Mode | Emits |\n|---|---|---|\n| \"review and grade\", \"is this safe to ship\", \"check this PR\" | **full** (default) | Findings, grade, deploy safety, commit dirt, ship gate |\n| \"findings only\", \"no grade\", \"line by line\", \"find the bugs\" | **`--findings-only`** | Findings, deploy safety, commit dirt, ship gate. No letters. |\n| \"grade only\", \"give it a letter\", \"A-F verdict\", \"should this merge\" | **`--grade-only`** | Lane grades, caps, required upgrades, ship gate. No findings list. |\n\nGrade-only still runs Step 1 (Instant-F) and still reads the code. It skips\nthe itemized findings output, not the investigation.\n\nOther modes that combine with any of the above:\n\n- **Plan review:** nothing built yet; check scope, sequencing, acceptance\n  criteria, test mapping, and missing decisions.\n- **Fix verification:** after fixes, rescan only the changed files and confirm\n  each original finding is gone.\n- **Release review:** add build, secrets, env, public copy, screenshots,\n  metadata, and live or API readback.\n- **`--fix`:** apply fixes (see Fix Mode).\n- **`--threat-verify`:** confirm declared threat-model mitigations exist.\n  Procedure in `references\u002Fthreat-verify.md`; read it only in this mode.\n\n**Depth** (state it at the top of every output):\n\n- `--quick` (about 2 min): pattern scan for obvious bugs, secrets, missing null\n  checks, injection, broken error handling. No cross-file analysis.\n- `--standard` (default, about 10 min): per-file correctness on changed paths,\n  language traps, state handling, test coverage of changed behavior, call graph\n  within changed files, maintainability baseline.\n- `--deep` (about 25 min): full import graph, call-chain tracing, whole-repo and\n  history pass, critic lanes. Use for auth, payments, migrations, public APIs.\n\nModel: Sonnet by default. Recommend Opus for auth, payments, and public API\nsurfaces.\n\n## Pre-flight\n\nName three things before analysis:\n\n- **Target:** repo, branch, PR, commit range, diff, route, API, or release build.\n- **Intent:** what the change claims to do. Find the spec in this order: issue\n  references in commits and PR body (`#123`, `Closes #45`), a path the caller\n  passed, a matching file under `docs\u002F` or `specs\u002F`. If none exists, write\n  \"no spec available\" and judge intent from the PR description alone. Never\n  invent requirements.\n- **Risk lanes:** frontend, backend, data, auth, payments, contracts, iOS,\n  release, public copy, analytics, secrets, deployment, docs.\n\nPin the comparison point and prove it is reviewable: `git rev-parse \u003Cbase>`\nresolves, diff with three dots (`git diff \u003Cbase>...HEAD`) so the comparison\nruns against the merge-base, and the diff is non-empty. A bad ref or empty\ndiff fails here in one line.\n\n## Context graph\n\nBuild it before judging the diff:\n\n1. Changed files and generated files.\n2. Imports, callers, routes, handlers, jobs, hooks, models, schemas, and\n   config or env dependencies the change touches.\n3. Tests, fixtures, migrations, release scripts, docs, and screenshots that\n   should move with the behavior.\n4. Runtime surfaces: local route, live URL, API endpoint, simulator flow,\n   dashboard, store metadata, deploy target.\n5. Domain contracts: ownership, rights and provenance, payments and wallets,\n   agent commerce, and published-statement accuracy.\n\nFlag beyond-the-diff risk when related files, defaults, docs, env, or deploy\nrequirements no longer agree.\n\n## Run the repo's own gates first\n\nDo not hand-review what a tool already decides. Detect what the repo ships\n(`package.json` scripts, config files, lockfiles) and run only that. Never add\na tool the repo does not use. Never report a result you did not run.\n\n| Stack | Type check | Lint | Test | Other |\n|---|---|---|---|---|\n| Web \u002F Node | `npx tsc --noEmit` | `npm run lint` (changed files) | `npm test` | `npm audit` when deps changed |\n| MCP server (Node) | `node --check \u003Cserver>.mjs` | configured linter | repo MCP tests | One stdio session: `initialize`, `notifications\u002Finitialized`, then list\u002Fcall\u002Fread\u002Fget |\n| iOS \u002F Swift | the build is the check | SwiftLint if configured | XCTest target | `xcodebuild -scheme X -destination 'platform=iOS Simulator,name=\u003Cdevice>' build` |\n| API \u002F backend | compile step if any | configured linter | contract or schema tests | OpenAPI validation against the live route |\n\nSeverity mapping: a type error on a changed line is P2 (P1 on a critical\npath); a failing test on changed behavior is P1; a test that silently stopped\nrunning is P2; a reachable, exploitable dependency CVE is P0 or P1; a verified\nlive secret is P0; a broken production build in a release review is P0.\n\nCite command, exit status, and the file:line it implicates. A gate that cannot\nrun goes in Verification as \"not run\" with the reason.\n\n**House rules bind.** Read `CLAUDE.md`, `AGENTS.md`, `CONTRIBUTING.md`,\n`.editorconfig`, and formatter, linter, or review config. Do not flag what a\nrule permits; do flag what it forbids. The nearest-ancestor rule wins for files\nunder its path. When the user dismisses a finding as deliberate, record it in\none line (pattern, why allowed, path scope) and do not raise it again.\n\n## Step 1: Instant-F triggers (always first, every mode)\n\nAny match is an automatic **F** and a P0 finding. Report file and line. Other\nlanes cannot raise the grade.\n\n- **Secrets:** hardcoded API key, token, or password in committed source; a\n  committed private key or certificate; a signing secret outside a secret\n  manager.\n- **Injection:** SQL built by string concatenation with user input; shell\n  command from user input via exec, spawn, or eval; unescaped user input\n  rendered where XSS is reachable.\n- **Auth bypass:** middleware with a skip path (early return, swallowed\n  exception, always-true condition); a permission check a request param can\n  bypass; JWT accepting `alg: none` or a hardcoded secret.\n- **Payments and wallets:** a handler that swallows errors; a webhook with no\n  signature verification; amount or recipient taken from untrusted input\n  without server-side validation.\n- **Data destruction:** a DROP or destructive ALTER with no rollback and no\n  tested restore; bulk delete or update with no WHERE or a user-controlled\n  WHERE; production cache wipes with no restore path.\n- **Plaintext sensitive data:** passwords stored or logged in plaintext; PII\n  sent to unencrypted logs or analytics; card, SSN, or health data in an\n  unencrypted field.\n\n## Step 2: Language and platform traps\n\nLoad only the sections that match the diff:\n\n- `references\u002Ftraps-web.md`: TypeScript, React, accessibility, Next.js, SEO\n  impact, database (Drizzle, Prisma), performance and Core Web Vitals.\n- `references\u002Ftraps-swift-ios.md`: Swift, SwiftUI, and client-server contract\n  drift for iOS.\n- `references\u002Fmaintainability-baseline.md`: twelve structural checks for\n  `--standard` and `--deep`, diff-scoped and always labeled as judgment.\n\n## Step 3: Security baseline\n\nRuns automatically when the diff touches `auth\u002F`, `api\u002F`, `middleware\u002F`,\n`routes\u002F`, `pages\u002Fapi\u002F`, or imports crypto, session, or payment modules. Cite\nthe category in each finding using the **OWASP Top 10:2025** numbering: A01\nBroken Access Control (now includes SSRF), A02 Security Misconfiguration, A03\nSoftware Supply Chain Failures, A04 Cryptographic Failures, A05 Injection, A06\nInsecure Design, A07 Authentication Failures, A08 Software or Data Integrity\nFailures, A09 Security Logging and Alerting Failures, A10 Mishandling of\nExceptional Conditions. API and mobile changes also map to the OWASP API\nSecurity Top 10 (2023) and MASVS. What counts as a finding per category is in\n`references\u002Fsecurity-baselines.md`.\n\n**Observability delta** (any new handler, endpoint, job, cron, or consumer):\nflag `catch` blocks that only `console.error` or swallow silently; new paths\nwith no log on entry or failure; React subtrees with no error boundary; new DB,\nexternal API, or model calls with no timing or trace span; analytics events\nthe old code fired and the new code dropped; background jobs that finish\nwithout logging count, duration, or failure reason.\n\n## Step 4: Deep pass (`--deep` only)\n\n- **Reverse dependencies:** find every caller of a changed function, type,\n  route, or constant across the repo. Name the call sites you checked.\n- **Shared assumptions:** for a changed schema, env var, default, or\n  invariant, find other places that assume the old value.\n- **History:** `git log -L` or `git blame` the touched lines. A change that\n  reintroduces a previously fixed shape is a regression; cite the prior commit.\n- **Sibling pattern:** compare to the nearest analog (other handlers, other\n  migrations). A lone handler skipping the shared auth wrapper is P1 even if\n  it works.\n- **Critic lanes** for auth, payments, migrations, or public APIs: a change\n  mapper, runtime critic, security critic, product critic, and test critic,\n  each reporting separately. Collect consensus. If a high-severity concern\n  survives a fix cycle, keep `hold` and name the smallest next check.\n\nA whole-repo claim with no named symbols is not evidence.\n\n## Step 5: Intent and scope\n\n- **Claim vs diff:** map each acceptance criterion to a code path or test.\n  Claimed behavior with no matching change is a P1 truth gap.\n- **Scope creep:** flag unrelated refactors, bundled dependency bumps, and\n  formatting sweeps that bury the change. Recommend a split.\n- **Effort signal:** state files and net lines changed and rate the review\n  effort: trivial, moderate, heavy, or too large to review safely.\n- **Walkthrough** (four or more files): a table of file, what changed, risk\n  lane. Add a mermaid `sequenceDiagram` or `flowchart` only when data crosses\n  three or more boundaries or an async, auth, or payment path changes.\n\n## Step 6: Grade (full and `--grade-only`)\n\nFor full and grade-only modes, read [the complete grading contract](references\u002Fgrading-contract.md) before assigning a grade. It defines all seven lanes, letter meanings, gate mapping, surface caps and debt weighting. An Instant-F or deploy-safety result still applies in every mode; never assign a letter from impression.\n\n## Step 7: Deploy safety (every mode, every run)\n\nRate each `pass | conditional | block`:\n\n- **Breaking changes:** a public API, schema, config key, or interface changes\n  with no versioned migration or fallback → block.\n- **Rollback safety:** `git revert` cannot undo it (migrations, sent email,\n  charges, deletes, storage writes, queue publishes) → block.\n- **Blast radius:** state it as `~0%` (flagged), `~partial` (one flow), or\n  `~100%` (shared middleware, auth, hot query).\n- **Environment readiness:** a required env var, secret, or flag is not in\n  production yet → block.\n- **Dependency changes:** new dependency with a known CVE, or unpinned in\n  production → block.\n- **Data mutations:** irreversible writes with no tested restore → block.\n- **Security delta:** improved, neutral, or new attack surface without\n  mitigation → block.\n- **Automation coverage:** no CI covering the changed surface, or required\n  checks not enforced on the default branch, in a production-connected repo →\n  block.\n\n## Step 8: Commit dirt (every mode, every run)\n\nRun the bundled scanner from the target repo instead of eyeballing:\n`bash \u003Cskill-dir>\u002Fscripts\u002Fcommit-dirt-scan.sh main...HEAD`, or pipe a diff\nwith `-`. It is read-only and always exits 0. Confirm each hit against the\ndiff before reporting. If it cannot run, check every added line by hand.\n\nSeven categories: secrets and credentials; debug artifacts; conflict markers;\nstaged build output (`node_modules\u002F`, `.next\u002F`, `dist\u002F`, `.DS_Store`, logs);\nWIP breadcrumbs (`DO NOT MERGE`, `TEMP:`, lorem ipsum); oversized or binary\nblobs over 500 KB; exposed internals (internal hosts, staging URLs, personal\nemails). Rate each `clean | suspicious | dirty`. Overall **DIRTY** is a P0\nfinding and moves the gate to `hold`. **SUSPICIOUS** is named for the reviewer\nto confirm.\n\n## Findings: format and precision\n\nLead with findings by severity. Group a repeated pattern once (\"appears in 4\nfiles: ...\"). If a structural defect exists, report it first and alone, and\nhold the line-level findings it governs as deferred.\n\nP0 and P1 use the full block:\n\n```\n[P0] path\u002Fto\u002Ffile.ts:142\nIssue: JWT secret falls back to empty string; any token is valid when SECRET is unset.\nFix: process.env.JWT_SECRET ?? (() => { throw new Error('JWT_SECRET required') })()\nVerify: set JWT_SECRET=\"\" and curl \u002Fapi\u002Fme: expect 401, currently 200.\nOWASP: A04:2025 Cryptographic Failures\nConfidence: high\n```\n\nP2 and P3 get one line each:\n\n```\n[P2] components\u002FFeed.tsx:88, index used as key on .map(); use item.id.\n```\n\n**Severity:** P0 data loss, security exposure, payment loss, broken release,\nor unsafe public behavior. P1 likely production regression, auth bug, broken\nprimary path, false published statement, missing deploy requirement. P2\nreal edge-case failure, incomplete state, test gap on changed behavior. P3\nlow-risk cleanup. A concern that cannot be tied to a file, route, command, or\nbehavior goes under Open Questions.\n\n**Confidence is observable:** `high` = reproduced, traced across the call\ngraph, or tied to a named failing input; `medium` = read, not executed;\n`low` = looks wrong, nothing proves it. Label every P0 and P1. A low-confidence\nsecurity suspicion keeps its severity with the label attached; low-confidence\nstyle notes collapse into one \"nitpicks\" line.\n\n**Before emitting, cut** anything with no file:line and fix, anything a gate\nalready reports, and anything that would not change the ship decision or earn\na human reviewer's comment.\n\n## Fix mode (`--fix` or an explicit request)\n\n1. Auto-apply local P2 and P3 fixes (single file, no contract change), one\n   commit per finding ID.\n2. Present P0 and P1 as fix briefs first: failing behavior and evidence, files\n   to open, expected change, acceptance criteria, verification command, WIP to\n   preserve. Never auto-apply to auth, payment, or migration code without\n   explicit confirmation.\n3. Re-run the relevant mode on changed files and mark each finding resolved or\n   escalated.\n4. Stop after 3 cycles on the same finding and escalate it as a design issue.\n\n## Suede-specific checks\n\nAuth and session behavior across app, API, native shells, and server ·\nrights, provenance, licensing, royalty, and agent-commerce claims match\nimplemented behavior · payment, wallet, x402, checkout, and credit flows fail\nclosed · public pages invent no metrics, pricing, partners, testimonials, or\nrelease promises · deploy and account assumptions match local guidance before\nproduction claims · store screenshots, metadata, and privacy answers match the\napp · migrations, env, flags, cron, queues, webhooks, and secrets are\ndocumented · contracts do not drift across web, backend, mobile, and docs.\n\n## Red flags: stop\n\n- \"CI is green, so it's fine.\" CI that never exercised the change is not\n  evidence.\n- \"The diff is small.\" Small diffs touch auth too. Step 1, 7, and 8 run every\n  time.\n- \"I wrote this, I know it works.\" Switch to review mode and hunt what your\n  implementation would miss.\n- \"The PR description explains it.\" Review the diff, not the story about it.\n- \"It was hard work, round up to B.\" Effort never moves a grade; evidence does.\n- \"Flag everything to be safe.\" Volume is noise. Run the precision cut.\n\n## Output\n\nOpen with **Simple explanation**: one plain paragraph a ten-year-old can follow\ncovering whether it passed and the single biggest reason. Then, by mode:\n\n```text\nDepth:\nFindings            (full, --findings-only)\nCode Grade          (full, --grade-only: 7 lanes + overall, cap applied, why, required upgrades)\nDeploy Safety       (all modes: 8 dimensions + SAFE TO DEPLOY | DEPLOY WITH CONDITIONS | DO NOT DEPLOY)\nCommit Dirt         (all modes: 7 categories + CLEAN | SUSPICIOUS | DIRTY)\nOpen Questions\nVerification        (checked \u002F not checked, with commands and exit codes)\nSHIP GATE: hold | ship-with-caveats | ship: [one sentence naming the blocker or caveat]\n```\n\nFor no findings, say so and name residual risk or unrun checks. To revise a\ngrade, name what changed. Silence means accepted.\n\nWorked examples, read only when calibrating: `references\u002Fworked-example.md`\n(a full pass on a real file) and `references\u002Fworked-example-grade-only.md`\n(lane arithmetic in grade-only mode).\n\n## Boundaries\n\n- Preserve user and other-agent WIP. Never stage, revert, or rewrite unrelated\n  files. Apply fixes only under Fix Mode.\n- Never invent tests, screenshots, live checks, deploy status, or gate results.\n- Never auto-apply fixes to auth, payment, or migration code without\n  confirmation.\n- A style choice no rule, formatter, or real cost governs is not a finding.\n\n## Routing\n\n- Make CI enforce the verdict on every merge → **suede-ci-gate**\n- The diff ships LLM, RAG, or agent behavior with no eval coverage →\n  **suede-ai-eval**\n- Several implementation plans need comparing before one multi-file change is\n  built → **suede-graph-flo-xr**\n- Fixes span several coordinated lanes → **suede-agent-teams**\n- The same value is stated on two surfaces that can drift →\n  **suede-parity-contract**\n\n## Worked contract\n\n[Worked contract](references\u002Fusage-contract.md) gives a bounded input, expected output and failure check for this workflow.\n",{"name":5,"metadata":55,"description":7},{"display-name":56},"Suede AI Code Skills","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-code",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":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-code",{"tool":73,"command":74},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-code",{"tool":76,"command":77},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-code","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-code\u002FSKILL.md",true,[81,87,91,95,99,103,107,111,115,119,123,127],{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"agents\u002Fopenai.yaml","REFERENCE","参考文档",436,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-code\u002Fagents\u002Fopenai.yaml",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"CARD.md",4471,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-code\u002FCARD.md",{"path":92,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fgrading-contract.md",3193,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-code\u002Freferences\u002Fgrading-contract.md",{"path":96,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fmaintainability-baseline.md",3496,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-code\u002Freferences\u002Fmaintainability-baseline.md",{"path":100,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fsecurity-baselines.md",3385,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-code\u002Freferences\u002Fsecurity-baselines.md",{"path":104,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fthreat-verify.md",1449,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-code\u002Freferences\u002Fthreat-verify.md",{"path":108,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Ftraps-swift-ios.md",3805,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-code\u002Freferences\u002Ftraps-swift-ios.md",{"path":112,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":113,"sourceHtmlUrl":114},"references\u002Ftraps-web.md",10932,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-code\u002Freferences\u002Ftraps-web.md",{"path":116,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":117,"sourceHtmlUrl":118},"references\u002Fusage-contract.md",845,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-code\u002Freferences\u002Fusage-contract.md",{"path":120,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":121,"sourceHtmlUrl":122},"references\u002Fworked-example-grade-only.md",8129,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-code\u002Freferences\u002Fworked-example-grade-only.md",{"path":124,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":125,"sourceHtmlUrl":126},"references\u002Fworked-example.md",11538,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-code\u002Freferences\u002Fworked-example.md",{"path":128,"resourceType":129,"resourceTypeDesc":130,"sizeBytes":131,"sourceHtmlUrl":132},"scripts\u002Fcommit-dirt-scan.sh","SCRIPT","脚本",3355,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-code\u002Fscripts\u002Fcommit-dirt-scan.sh",[134,144,152,160,168,176],{"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":138,"licenseFileUrl":139,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":143},"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":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":138,"licenseFileUrl":148,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":143},"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":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":138,"licenseFileUrl":156,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":143},"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":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":138,"licenseFileUrl":164,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":143},"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":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":138,"licenseFileUrl":172,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":143},"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":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":138,"licenseFileUrl":180,"sourceHtmlUrl":181,"categories":182,"keywords":183,"publishedAt":143},"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",[],[]]