[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"extension-skill-j4rk0r-usage-tracker-zh-CN":3,"guides-for-j4rk0r-usage-tracker":420,"similar-k17cpt5vz9ykrzyec6gvpksy6x86m3ss-zh-CN":421},{"_creationTime":4,"_id":5,"children":6,"community":7,"display":9,"evaluation":15,"identity":236,"isFallback":223,"parentExtension":241,"providers":242,"relations":248,"repo":251,"tags":416,"workflow":417},1778691484298.108,"k17cpt5vz9ykrzyec6gvpksy6x86m3ss",[],{"reviewCount":8},0,{"description":10,"installMethods":11,"name":13,"sourceUrl":14},"跟踪每次本地 Claude Code 使用情况并进行报告：消耗的 token 数、预估成本（欧元）、会话数、项目数以及工具细分。当用户询问有关消耗、积分、使用情况、每次请求的成本、想要查看报告、询问特定请求为何昂贵、怀疑某个进程正在消耗 token、想要优化 Claude Code 使用情况或想要审核每次请求的工具使用情况时使用。还会触发对西班牙语短语的响应：'cuánto me está costando', 'cuántos tokens', 'consumo de hoy', 'qué petición fue cara', 'está consumiendo mucho', 'optimizar consumo', 'reporte de uso', 'ver uso', 'instalar tracker', 'hook no registra'。命令：/usage-tracker report [hoy|semana|mes|all] [proyecto], /usage-tracker top-requests [hoy|semana], /usage-tracker install, /usage-tracker status",{"claudeCode":12},"j4rk0r/claude-skills","usage-tracker","https://github.com/j4rk0r/claude-skills",{"_creationTime":16,"_id":17,"extensionId":5,"locale":18,"result":19,"trustSignals":221,"workflow":234},1778691484298.1082,"kn79qks09z45zsmzx8ff9bmr5n86n685","zh-CN",{"checks":20,"evaluatedAt":192,"extensionSummary":193,"features":194,"nonGoals":199,"promptVersionExtension":203,"promptVersionScoring":204,"purpose":205,"rationale":206,"score":207,"summary":208,"tags":209,"tier":215,"useCases":216},[21,26,29,32,36,39,43,47,50,53,57,61,65,69,72,75,78,81,84,87,91,95,99,103,107,110,113,116,120,123,126,129,132,135,138,142,146,150,153,157,160,163,166,169,173,176,179,182,185,189],{"category":22,"check":23,"severity":24,"summary":25},"Practical Utility","Problem relevance","pass","描述清楚地确定了跟踪和理解每次请求的本地 Claude Code 使用成本的问题，并提供了使用该技能的具体触发条件。",{"category":22,"check":27,"severity":24,"summary":28},"Unique selling proposition","该技能通过提供详细的、每次请求级别的成本跟踪和分析，提供了超越默认 LLM 功能的显著价值，而这不是内置功能。",{"category":22,"check":30,"severity":24,"summary":31},"Production readiness","该技能看起来已准备好投入生产，具有清晰的安装、配置和报告命令，涵盖了使用跟踪的整个生命周期。",{"category":33,"check":34,"severity":24,"summary":35},"Scope","Single responsibility principle","该扩展仅专注于跟踪和报告 Claude Code 使用情况，而不涉及不相关的领域。",{"category":33,"check":37,"severity":24,"summary":38},"Description quality","描述准确简洁地反映了该技能的功能，包括其触发条件和命令，并且格式良好。",{"category":40,"check":41,"severity":24,"summary":42},"Invocation","Scoped tools","该技能使用特定的、狭窄的工具（Bash、用于解析/报告的 Python 脚本、文件操作），而不是单一的通用命令。",{"category":44,"check":45,"severity":24,"summary":46},"Documentation","Configuration & parameter reference","SKILL.md 详细介绍了功能、命令，并提供了安装和报告脚本，并对成本和限制进行了清晰的解释。",{"category":33,"check":48,"severity":24,"summary":49},"Tool naming","脚本和命令中的工具名称具有描述性，并符合预期的命名约定。",{"category":33,"check":51,"severity":24,"summary":52},"Minimal I/O surface","使用的工具（Bash、Python）操作特定的日志文件和配置，并且输出脚本提供汇总报告而不是原始数据转储。",{"category":54,"check":55,"severity":24,"summary":56},"License","License usability","该项目已获得 MIT 许可，这是一个宽松的开源许可证。",{"category":58,"check":59,"severity":24,"summary":60},"Maintenance","Commit recency","最后一次提交是在 2026 年 4 月 13 日，这是最近的。",{"category":58,"check":62,"severity":63,"summary":64},"Dependency Management","not_applicable","该技能依赖于标准的 shell 实用程序和 Python，这些被假定为可用并由 Claude Code 环境管理。",{"category":66,"check":67,"severity":24,"summary":68},"Security","Secret Management","该技能不处理或暴露任何秘密；它操作本地日志文件和配置。",{"category":66,"check":70,"severity":24,"summary":71},"Injection","该技能使用标准的 Bash 和 Python 脚本，操作本地文件，并且不执行不受信任的外部数据作为指令。",{"category":66,"check":73,"severity":24,"summary":74},"Transitive Supply-Chain Grenades","该技能依赖于本地脚本和标准工具，没有运行时获取外部代码或数据。",{"category":66,"check":76,"severity":24,"summary":77},"Sandbox Isolation","该技能在用户的主目录中操作日志文件和配置，并使用标准工具，不尝试访问此范围之外的区域。",{"category":66,"check":79,"severity":24,"summary":80},"Sandbox escape primitives","在提供的脚本中未发现分离的进程启动或拒绝-重试循环。",{"category":66,"check":82,"severity":24,"summary":83},"Data Exfiltration","该技能的主要功能是记录本地使用数据，并且不向第三方提交任何数据。",{"category":66,"check":85,"severity":24,"summary":86},"Hidden Text Tricks","捆绑的内容似乎没有隐藏的操纵技巧，并且描述使用了标准的 ASCII 字符。",{"category":88,"check":89,"severity":24,"summary":90},"Hooks","Opaque code execution","提供的 Bash 和 Python 脚本是纯文本、可读的源代码。",{"category":92,"check":93,"severity":24,"summary":94},"Portability","Structural Assumption","该技能假定存在标准文件位置，如 ~/.claude/，并尽可能使用相对路径，并提供清晰的安装文档。",{"category":96,"check":97,"severity":24,"summary":98},"Trust","Issues Attention","存储库中没有报告未解决的问题，表明维护活跃或没有近期问题。",{"category":100,"check":101,"severity":24,"summary":102},"Versioning","Release Management","该项目通过 Git 提交进行跟踪，虽然没有明确详细说明像 semver 这样的正式版本控制系统，但提交历史表明了积极的开发。",{"category":104,"check":105,"severity":24,"summary":106},"Code Execution","Validation","用于解析日志数据的 Python 脚本包含 JSON 解析的错误处理，Bash 脚本则对过滤器和路径使用参数验证。",{"category":66,"check":108,"severity":24,"summary":109},"Unguarded Destructive Operations","该技能主要执行日志记录和报告；不存在文件删除等破坏性操作，脚本安装涉及标准的 chmod 操作。",{"category":104,"check":111,"severity":24,"summary":112},"Error Handling","提供的脚本包含文件操作、JSON 解析和用户输入验证的错误处理，能优雅地退出或报告问题。",{"category":104,"check":114,"severity":24,"summary":115},"Logging","该技能的核心功能是创建本地审计日志（~/.claude/usage.jsonl），捕获详细的使用信息。",{"category":117,"check":118,"severity":24,"summary":119},"Compliance","GDPR","该技能跟踪本地使用情况，不处理发送给第三方的个人数据。项目名称由用户定义。",{"category":117,"check":121,"severity":24,"summary":122},"Target market","该技能专为本地使用跟踪而设计，不受地域或法律限制，因此其目标市场是全球性的。",{"category":92,"check":124,"severity":24,"summary":125},"Runtime stability","该技能依赖于标准的 Bash 和 Python，这些在广泛可用，并且其安装过程有清晰的文档记录。",{"category":44,"check":127,"severity":24,"summary":128},"README","README.md 提供了该技能的全面概述、其目的、安装以及存储库中的其他相关技能。",{"category":33,"check":130,"severity":24,"summary":131},"Tool surface size","该扩展公开了一组专注的命令和底层脚本，符合可管理性的理想范围。",{"category":40,"check":133,"severity":24,"summary":134},"Overlapping near-synonym tools","命令和内部工具具有不同的目的（report、install、status、top-requests），并且没有重叠的近义词。",{"category":44,"check":136,"severity":24,"summary":137},"Phantom features","所有宣传的功能，如日志记录、报告命令和安装，都在提供的脚本和文档中有相应的实现。",{"category":139,"check":140,"severity":24,"summary":141},"Install","Installation instruction","README 和 SKILL.md 提供了清晰的安装说明，包括可复制粘贴的命令和验证步骤。",{"category":143,"check":144,"severity":24,"summary":145},"Errors","Actionable error messages","脚本提供信息性的错误消息，例如指示日志文件丢失或 JSON 解析失败，并提供如何继续的指导。",{"category":147,"check":148,"severity":24,"summary":149},"Execution","Pinned dependencies","该技能使用标准的系统实用程序（Bash、Python）并且不引入需要固定的第三方依赖项。",{"category":33,"check":151,"severity":63,"summary":152},"Dry-run preview","该技能的操作主要是数据日志记录和报告；没有需要 dry-run 模式的状态更改或向外发送的命令。",{"category":154,"check":155,"severity":24,"summary":156},"Protocol","Idempotent retry & timeouts","操作是本地文件读写，在此上下文中本质上是幂等的，并且脚本设计为能够优雅地处理错误，而不是依赖重试。",{"category":117,"check":158,"severity":24,"summary":159},"Telemetry opt-in","该技能的日志记录是本地的，并且性质上是 opt-in 的（通过其安装过程）；没有向外部发出遥测数据。",{"category":40,"check":161,"severity":24,"summary":162},"Precise Purpose","SKILL.md 清楚地说明了目的（跟踪本地 Claude Code 使用情况）并提供了其使用的特定触发条件和命令。",{"category":40,"check":164,"severity":24,"summary":165},"Concise Frontmatter","SKILL.md 的 frontmatter 简洁、独立，并准确地总结了核心功能和触发条件。",{"category":44,"check":167,"severity":24,"summary":168},"Concise Body","SKILL.md 的正文结构良好，对细节使用了渐进式披露，并且长度合理。",{"category":170,"check":171,"severity":24,"summary":172},"Context","Progressive Disclosure","提供了详细的解释和脚本（直接提供或通过引用链接），以便清晰理解，而不会使主文档过于冗长。",{"category":170,"check":174,"severity":63,"summary":175},"Forked exploration","该技能专注于本地使用跟踪和报告，而不是深入的探索或代码审查，因此 forked context 不适用。",{"category":22,"check":177,"severity":24,"summary":178},"Usage examples","SKILL.md 和 README 提供了报告和安装等命令的清晰示例，展示了它们的使用和预期输出。",{"category":22,"check":180,"severity":24,"summary":181},"Edge cases","SKILL.md 解决了潜在问题，如损坏的 JSON 日志、缺失的 hook 和权限错误，并提供了具体的诊断步骤和恢复程序。",{"category":104,"check":183,"severity":63,"summary":184},"Tool Fallback","该技能依赖于标准的系统工具和自己的脚本，而不是需要备用方案的外部 MCP 服务器或其他技能。",{"category":186,"check":187,"severity":24,"summary":188},"Safety","Halt on unexpected state","脚本包含对文件存在性、JSON 有效性和权限的检查，在意外状态下会停止执行并显示信息性消息。",{"category":92,"check":190,"severity":24,"summary":191},"Cross-skill coupling","usage-tracker 技能独立运行，不隐式依赖其他技能；其功能是自包含的。",1778691352775,"该技能作为 PostToolUse hook，记录每次工具调用的详细信息，包括消耗的 token 数、预估成本、项目、会话以及触发它的用户请求。它提供了安装、报告和状态检查脚本，旨在使使用情况透明化。",[195,196,197,198],"记录每次工具调用的相关数据。","根据模型和 token 计算预估成本。","按请求、项目、会话和工具聚合使用数据。","提供安装、报告和状态命令。",[200,201,202],"Claude Max 订阅的实时成本跟踪（仅提供相对索引）。","跟踪 Claude 制作的外部 API 调用。","替换官方 Claude 账单报告（侧重于本地、每次请求的分析）。","3.0.0","4.4.0","为用户提供对本地 Claude Code token 消耗和每次请求、项目和会话的预估成本的详细了解，从而能够更好地优化和审计使用情况。","所有检查均以“pass”严重性通过，表明在所有评估维度上都具有高质量和最佳实践的遵循。",100,"一个高质量的技能，用于详细的本地 Claude Code 使用情况跟踪和报告。",[210,211,212,213,214],"logging","cost-tracking","usage-analysis","development-tools","auditing","verified",[217,218,219,220],"当用户询问有关消耗、积分或使用成本时。","查看详细的 token 使用情况报告。","了解特定请求为何昂贵。","按每次请求或项目审核工具使用情况。",{"codeQuality":222,"collectedAt":224,"documentation":225,"maintenance":228,"security":231,"testCoverage":233},{"hasLockfile":223},false,1778691335414,{"descriptionLength":226,"readmeSize":227},788,26542,{"closedIssues90d":8,"forks":8,"hasChangelog":223,"openIssues90d":8,"pushedAt":229,"stars":230},1776088077000,2,{"hasNpmPackage":223,"license":232,"smitheryVerified":223},"MIT",{"hasCi":223,"hasTests":223},{"updatedAt":235},1778691484298,{"basePath":237,"githubOwner":238,"githubRepo":239,"locale":18,"slug":13,"type":240},"skills/usage-tracker","j4rk0r","claude-skills","skill",null,{"evaluate":243,"extract":246},{"promptVersionExtension":203,"promptVersionScoring":204,"score":207,"tags":244,"targetMarket":245,"tier":215},[210,211,212,213,214],"global",{"commitSha":247},"HEAD",{"repoId":249,"translatedFrom":250},"kd79shaph0e07035621cxd7x1n86m944","k1760f97f0gchra7wpw9wk3xtx86nhzf",{"_creationTime":252,"_id":249,"identity":253,"providers":254,"workflow":412},1778689957073.3262,{"githubOwner":238,"githubRepo":239,"sourceUrl":14},{"classify":255,"discover":399,"github":402},{"commitSha":247,"extensions":256},[257,289,306,327,352,366,377,387],{"basePath":258,"description":259,"displayName":260,"installMethods":261,"rationale":262,"selectedPaths":263,"source":287,"sourceLanguage":288,"type":240},"skills/codex-diff-develop","Revisa el diff de la rama actual frente a develop en proyectos Drupal 11 siguiendo la metodología Codex (lógica de negocio, edge cases de hooks/queries, seguridad, performance, completitud). Genera un informe .md en la carpeta del IDE detectado (.antigravity/, .cursor/, .vscode/ o docs/) con hallazgos por severidad y soluciones accionables. Usar cuando el usuario pida \"Revisión diff develop\", \"revisión diff develop\", \"diff develop\", \"revisar diff\", \"codex diff\" o expresiones similares con intención de auditar cambios contra develop. Triggers: diff develop, codex diff, revisión diff, lint diff develop, auditar diff.","codex-diff-develop",{"claudeCode":12},"SKILL.md frontmatter at skills/codex-diff-develop/SKILL.md",[264,267,270,273,275,277,279,281,283,285],{"path":265,"priority":266},"SKILL.md","mandatory",{"path":268,"priority":269},"README.md","high",{"path":271,"priority":272},"README.de.md","medium",{"path":274,"priority":272},"README.es.md",{"path":276,"priority":272},"README.fr.md",{"path":278,"priority":272},"README.ja.md",{"path":280,"priority":272},"README.pt.md",{"path":282,"priority":272},"README.zh.md",{"path":284,"priority":272},"references/metodologia-codex-completa.md",{"path":286,"priority":272},"references/plantillas-hallazgos.md","rule","es",{"basePath":290,"description":291,"displayName":292,"installMethods":293,"rationale":294,"selectedPaths":295,"source":287,"sourceLanguage":288,"type":240},"skills/codex-pr-review","Revisa pull requests en proyectos Drupal 11 (u otro) siguiendo la metodología Codex (lógica de negocio, edge cases de hooks/queries, seguridad, performance, completitud). Genera un informe .md en la carpeta del IDE detectado (.antigravity/, .cursor/, .vscode/ o docs/) con hallazgos por severidad y soluciones accionables. Usar cuando el usuario pida \"revisión Codex\", \"revisión de PR\", \"revisar PR\", \"revisar PR","codex-pr-review",{"claudeCode":12},"SKILL.md frontmatter at skills/codex-pr-review/SKILL.md",[296,297,298,299,300,301,302,303,304,305],{"path":265,"priority":266},{"path":268,"priority":269},{"path":271,"priority":272},{"path":274,"priority":272},{"path":276,"priority":272},{"path":278,"priority":272},{"path":280,"priority":272},{"path":282,"priority":272},{"path":284,"priority":272},{"path":286,"priority":272},{"basePath":307,"description":308,"displayName":309,"installMethods":310,"rationale":311,"selectedPaths":312,"source":287,"sourceLanguage":288,"type":240},"skills/lint-drupal-module","Lint review completo de un módulo Drupal 11 combinando 4 fuentes en paralelo — PHPStan level 5 + phpstan-drupal, PHPCS Drupal/DrupalPractice, agente drupal-qa (estándares) y agente drupal-security (OWASP). Dos modos — completo (todo el módulo) y diff (solo archivos cambiados vs develop). Genera informe markdown estructurado en la carpeta del IDE con resumen ejecutivo, hallazgos clasificados por severidad, acciones P0/P1/P2 y comandos de verificación. Úsalo siempre que el usuario quiera auditar calidad o seguridad de un módulo Drupal custom, aunque no diga \"lint\". Triggers — \"lint review\", \"lint del módulo\", \"auditar módulo Drupal\", \"revisar módulo custom\", \"phpstan del módulo\", \"validar módulo\", \"qa del módulo\", o cuando el usuario pregunta \"¿está bien este módulo?\", \"¿hay errores?\", \"¿es seguro?\". También antes de un release, antes de un PR a develop, o al validar un módulo recién creado.","lint-drupal-module",{"claudeCode":12},"SKILL.md frontmatter at skills/lint-drupal-module/SKILL.md",[313,314,315,316,317,318,319,320,321,323,325],{"path":265,"priority":266},{"path":268,"priority":269},{"path":271,"priority":272},{"path":274,"priority":272},{"path":276,"priority":272},{"path":278,"priority":272},{"path":280,"priority":272},{"path":282,"priority":272},{"path":322,"priority":272},"references/edge-cases.md",{"path":324,"priority":272},"references/plantilla-informe.md",{"path":326,"priority":272},"references/prompts-agentes.md",{"basePath":328,"description":329,"displayName":330,"installMethods":331,"rationale":332,"selectedPaths":333,"source":287,"sourceLanguage":288,"type":240},"skills/milestone","Persistent development milestone tracker with full context across conversations. Use when: tracking multi-session features, resuming work from a previous conversation, asking 'what's left to do on X' or 'what's pending', breaking work into trackable subtasks, planning complex implementations, updating progress after coding, checking project status, completing a subtask with QA validation, auditing what's missing in the project, syncing milestones with actual code state, or closing/archiving a finished milestone. Also trigger when user references a milestone by name, says 'what did we do last time', 'resume where we left off', 'how far along is X', 'mark this as done', 'milestone done', 'close this milestone', 'what's missing', 'audit the project', 'sync milestones', or wants to plan a feature with subtasks. Commands: /milestone, /milestone \u003Cname>, /milestone init, /milestone sync, /milestone start, /milestone done, /milestone update.","milestone",{"claudeCode":12},"SKILL.md frontmatter at skills/milestone/SKILL.md",[334,335,336,337,338,339,340,341,342,344,346,348,350],{"path":265,"priority":266},{"path":268,"priority":269},{"path":271,"priority":272},{"path":274,"priority":272},{"path":276,"priority":272},{"path":278,"priority":272},{"path":280,"priority":272},{"path":282,"priority":272},{"path":343,"priority":272},"references/errors.md",{"path":345,"priority":272},"references/milestone-new-session.sh",{"path":347,"priority":272},"references/project-audit.md",{"path":349,"priority":272},"references/qa-validation.md",{"path":351,"priority":272},"references/templates.md",{"basePath":353,"description":354,"displayName":355,"installMethods":356,"rationale":357,"selectedPaths":358,"source":287,"sourceLanguage":365,"type":240},"skills/skill-advisor","Pre-execution assistant that builds a full execution plan with installed skills (✅) AND uninstalled gaps (❌) the task needs, then offers to install missing skills one by one. Use BEFORE starting any multi-step task. Triggers: 'recommend skills', 'what skill should I use', 'advise', 'suggest', 'help me with', or any work instruction involving code, design, planning, debugging, docs, testing, commits, PRs, strategy.","skill-advisor",{"claudeCode":12},"SKILL.md frontmatter at skills/skill-advisor/SKILL.md",[359,360,361,363],{"path":265,"priority":266},{"path":268,"priority":269},{"path":362,"priority":272},"references/gap-maps.md",{"path":364,"priority":272},"references/pipelines.md","en",{"basePath":367,"description":368,"displayName":369,"installMethods":370,"rationale":371,"selectedPaths":372,"source":287,"sourceLanguage":365,"type":240},"skills/skill-guard","Security auditor for Claude Code skills. Analyzes skills BEFORE installation using a 9-layer threat detection engine (permissions, static patterns, LLM semantic analysis, bundled scripts, data flow, MCP abuse, supply chain, reputation, anti-evasion) with scoring 0-100 and community audit registry. MUST be used whenever the user is about to install a skill — via npx skills add, /find-skills recommendation, /skill-advisor suggestion, or manual request. Also use when user says 'is this skill safe', 'audit this skill', 'check this skill', 'security scan', 'review before installing', or any mention of skill safety/trust/security. Intercept ALL skill installations proactively.","skill-guard",{"claudeCode":12},"SKILL.md frontmatter at skills/skill-guard/SKILL.md",[373,374,375],{"path":265,"priority":266},{"path":268,"priority":269},{"path":376,"priority":272},"references/patterns.md",{"basePath":378,"description":379,"displayName":380,"installMethods":381,"rationale":382,"selectedPaths":383,"source":287,"sourceLanguage":365,"type":240},"skills/skill-learner","Persistent correction system that captures mistakes from skills or Claude behavior and ensures they never repeat across sessions. Use whenever the user indicates something went wrong — \"that's wrong\", \"fix this\", \"not what I wanted\", \"learn from this\", \"don't do that again\", \"esto está mal\", \"aprende de esto\", \"no hagas eso otra vez\", or any correction, complaint, or teaching moment about Claude's output or a skill's behavior. Also use when the user asks to review, list, delete, or manage past corrections, or wants to create an improvement proposal for a skill author. Covers installed skills, general Claude behavior, and cross-session learning persistence.\n","skill-learner",{"claudeCode":12},"SKILL.md frontmatter at skills/skill-learner/SKILL.md",[384,385],{"path":265,"priority":266},{"path":386,"priority":272},"references/correction-patterns.md",{"basePath":237,"description":388,"displayName":13,"installMethods":389,"rationale":390,"selectedPaths":391,"source":287,"sourceLanguage":288,"type":240},"Track and report local Claude Code usage per request: tokens consumed, estimated cost in €, sessions, projects, and tool breakdown. Use when the user asks about consumption, credits, usage, cost per request, wants to see a report, asks why a specific request was expensive, suspects a process is consuming tokens, wants to optimize their Claude Code usage, or wants to audit tool usage by request. Also triggers on Spanish phrases: 'cuánto me está costando', 'cuántos tokens', 'consumo de hoy', 'qué petición fue cara', 'está consumiendo mucho', 'optimizar consumo', 'reporte de uso', 'ver uso', 'instalar tracker', 'hook no registra'. Commands: /usage-tracker report [hoy|semana|mes|all] [proyecto], /usage-tracker top-requests [hoy|semana], /usage-tracker install, /usage-tracker status",{"claudeCode":12},"SKILL.md frontmatter at skills/usage-tracker/SKILL.md",[392,393,395,397],{"path":265,"priority":266},{"path":394,"priority":272},"references/log-usage.sh",{"path":396,"priority":272},"references/pricing.md",{"path":398,"priority":272},"references/usage-report.sh",{"sources":400},[401],"manual",{"closedIssues90d":8,"description":403,"forks":8,"homepage":404,"license":232,"openIssues90d":8,"pushedAt":229,"readmeSize":227,"stars":230,"topics":405},"Curated high-quality skills for Claude Code — skill-advisor and more","https://claude-skills-omega.vercel.app",[406,407,408,409,410,239,411,355],"agent-skills","ai-tools","anthropic","claude","claude-code","developer-tools",{"classifiedAt":413,"discoverAt":414,"extractAt":415,"githubAt":415,"updatedAt":413},1778691193146,1778689957073,1778691191083,[214,211,213,210,212],{"evaluatedAt":418,"extractAt":419,"updatedAt":235},1778691352986,1778691193352,[],[422,452,480,502,531,562],{"_creationTime":423,"_id":424,"community":425,"display":426,"identity":432,"providers":436,"relations":445,"tags":448,"workflow":449},1778695548458.3718,"k175vfqr247swcyt62e6v08a4x86mtf1",{"reviewCount":8},{"description":427,"installMethods":428,"name":430,"sourceUrl":431},"Investigate root causes and manage CAPAs (Corrective and Preventive Actions) for compliance deviations. Covers investigation method selection (5-Why, fishbone, fault tree), structured root cause analysis, corrective vs preventive action design, effectiveness verification, and trend analysis. Use when an audit finding requires a CAPA, when a deviation or incident occurs in a validated system, when a regulatory observation needs a formal response, when a data integrity anomaly requires investigation, or when recurring issues suggest a systemic root cause.\n",{"claudeCode":429},"pjt222/agent-almanac","investigate-capa-root-cause","https://github.com/pjt222/agent-almanac",{"basePath":433,"githubOwner":434,"githubRepo":435,"locale":365,"slug":430,"type":240},"skills/investigate-capa-root-cause","pjt222","agent-almanac",{"evaluate":437,"extract":444},{"promptVersionExtension":203,"promptVersionScoring":204,"score":207,"tags":438,"targetMarket":245,"tier":215},[439,440,441,442,443,214],"compliance","capa","investigation","root-cause-analysis","gxp",{"commitSha":247},{"parentExtensionId":446,"repoId":447},"k170h0janaa9kwn7cfgfz2ykss86mmh9","kd7aryv63z61j39n2td1aeqkvh86mh12",[214,440,439,443,441,442],{"evaluatedAt":450,"extractAt":451,"updatedAt":450},1778699030088,1778695548458,{"_creationTime":453,"_id":454,"community":455,"display":456,"identity":462,"providers":466,"relations":474,"tags":476,"workflow":477},1778695753353.633,"k17fxb9fnez7bhk0sy8znxzx8n86m48r",{"reviewCount":8},{"description":457,"installMethods":458,"name":460,"sourceUrl":461},"Drift detection + baseline integrity guard for agent workspace files with automatic alerting support",{"claudeCode":459},"prompt-security/clawsec","soul-guardian","https://github.com/prompt-security/clawsec",{"basePath":463,"githubOwner":464,"githubRepo":465,"locale":365,"slug":460,"type":240},"skills/soul-guardian","prompt-security","clawsec",{"evaluate":467,"extract":473},{"promptVersionExtension":203,"promptVersionScoring":204,"score":207,"tags":468,"targetMarket":245,"tier":215},[469,470,214,471,472],"security","integrity","file-guard","workspace",{"commitSha":247},{"repoId":475},"kd72phsqkbk8w57ctvf7ac9nqs86n9t4",[214,471,470,469,472],{"evaluatedAt":478,"extractAt":479,"updatedAt":478},1778696065248,1778695753353,{"_creationTime":481,"_id":482,"community":483,"display":484,"identity":488,"providers":490,"relations":498,"tags":499,"workflow":500},1778695548458.3328,"k17cyw0d6mk1vdgew2xmncx1f186npdm",{"reviewCount":8},{"description":485,"installMethods":486,"name":487,"sourceUrl":431},"Audit project dependencies for version staleness, security vulnerabilities, and compatibility issues. Covers lock file analysis, upgrade path planning, and breaking change assessment. Use before a release to ensure dependencies are current and secure, during periodic maintenance reviews, after receiving a security advisory, when upgrading to a new language version, before submitting to CRAN or npm, or when inheriting a project to assess its dependency health.\n",{"claudeCode":429},"audit-dependency-versions",{"basePath":489,"githubOwner":434,"githubRepo":435,"locale":365,"slug":487,"type":240},"skills/audit-dependency-versions",{"evaluate":491,"extract":497},{"promptVersionExtension":203,"promptVersionScoring":204,"score":207,"tags":492,"targetMarket":245,"tier":215},[493,214,469,494,495,496],"dependencies","upgrades","versioning","maintenance",{"commitSha":247},{"parentExtensionId":446,"repoId":447},[214,493,496,469,494,495],{"evaluatedAt":501,"extractAt":451,"updatedAt":501},1778696062378,{"_creationTime":503,"_id":504,"community":505,"display":506,"identity":512,"providers":517,"relations":525,"tags":527,"workflow":528},1778694720643.034,"k175824bv0hy06y0gygd192pgd86nceh",{"reviewCount":8},{"description":507,"installMethods":508,"name":510,"sourceUrl":511},"Run a weekly SEO review for one registered website, write audit artifacts, and choose the next best safe action.",{"claudeCode":509},"nowork-studio/toprank","Toprank Weekly Review","https://github.com/nowork-studio/toprank",{"basePath":513,"githubOwner":514,"githubRepo":515,"locale":365,"slug":516,"type":240},"openclaw/skills/toprank-weekly-review","nowork-studio","toprank","toprank-weekly-review",{"evaluate":518,"extract":524},{"promptVersionExtension":203,"promptVersionScoring":204,"score":207,"tags":519,"targetMarket":245,"tier":215},[520,521,522,214,523],"seo","google-ads","meta-ads","automation",{"commitSha":247,"license":232},{"repoId":526},"kd74wn8s89tp9hrfsmcra492r586nbrv",[214,523,521,522,520],{"evaluatedAt":529,"extractAt":530,"updatedAt":529},1778694967711,1778694720643,{"_creationTime":532,"_id":533,"community":534,"display":535,"identity":541,"providers":545,"relations":553,"tags":557,"workflow":558},1778692169475.437,"k172w1s4pv9xgb31fp2vrtv04186n44y",{"reviewCount":8},{"description":536,"installMethods":537,"name":539,"sourceUrl":540},"显示每个技能消耗的上下文窗口令牌数量。当用户询问有关令牌成本、上下文预算、技能大小，或希望了解哪些技能浪费了最多的上下文空间时使用。",{"claudeCode":538},"khendzel/skills-janitor","janitor-tokens","https://github.com/khendzel/skills-janitor",{"basePath":542,"githubOwner":543,"githubRepo":544,"locale":18,"slug":539,"type":240},"skills/janitor-tokens","khendzel","skills-janitor",{"evaluate":546,"extract":552},{"promptVersionExtension":203,"promptVersionScoring":204,"score":207,"tags":547,"targetMarket":245,"tier":215},[548,549,550,551,214],"skills-management","code-analysis","cost-optimization","token-usage",{"commitSha":247},{"parentExtensionId":554,"repoId":555,"translatedFrom":556},"k173y287h96a0x42zvrvymzvgn86nq38","kd722xn3d2v8ze2vwgebvzgpv986mj48","k17epektyn71reavpa0hvxmvch86mxwf",[214,549,550,548,551],{"evaluatedAt":559,"extractAt":560,"updatedAt":561},1778692064277,1778691884319,1778692169475,{"_creationTime":563,"_id":564,"community":565,"display":566,"identity":570,"providers":572,"relations":578,"tags":580,"workflow":581},1778692149990.924,"k1784mxj5rt2pfmfdqhc36xnys86nnwc",{"reviewCount":8},{"description":567,"installMethods":568,"name":569,"sourceUrl":540},"一个完整的报告，用于检查所有技能的健康状况。当用户想要检查错误、查找重复项、检测损坏的技能或获取技能健康状况的完整概览时使用。",{"claudeCode":538},"janitor-report",{"basePath":571,"githubOwner":543,"githubRepo":544,"locale":18,"slug":569,"type":240},"skills/janitor-report",{"evaluate":573,"extract":577},{"promptVersionExtension":203,"promptVersionScoring":204,"score":207,"tags":574,"targetMarket":245,"tier":215},[575,576,214,496,411],"skills","management",{"commitSha":247},{"parentExtensionId":554,"repoId":555,"translatedFrom":579},"k177wxk7zzyaycd3t6ads36e7586mkcw",[214,411,496,576,575],{"evaluatedAt":582,"extractAt":560,"updatedAt":583},1778692022779,1778692149990]