搜索「Literature Review」的结果

io.clawhub.adamsardo/codex-sub-agents

使用 OpenAI Codex CLI 完成编码任务。触发词：codex、code review、修复 CI、重构代码、实现功能、编码智能体、gpt-5-codex。让 Clawdbot 以子代理或直接工具的方式将编码工作委托给 Codex CLI。

io.clawhub.fetcher-sh/app-store-api

An Apple App Store API alternative on fetcher.sh — pay-per-call in USDC via x402, or prepaid credits with a Bearer key, no Apple Developer Program membership. Use when the user wants to search iOS apps by keyword in any country's storefront, fetch an app's or app bundle's full details, reviews sorted by recent/helpful, apps similar to a given app, search or fetch app bundles, or fetch a developer's app catalog. Also covers iOS app store optimization (ASO) research, competitor app monitoring, localized storefront comparison, and app discovery without Apple Developer Program access.

io.clawhub.fetcher-sh/yelp-api

A Yelp API alternative on fetcher.sh — pay-per-call in USDC via x402, or prepaid credits with a Bearer key, no Yelp Fusion API app approval. Use when the user wants to search local businesses by query and location sorted by rating or review count, fetch a business's full details by ID or by its Yelp URL handle/slug, or fetch a business's reviews. Also covers local business discovery, restaurant/service research, review sentiment input, and competitor monitoring for local businesses without Yelp Fusion API's app-approval process and daily call caps.

io.clawhub.fetcher-sh/google-play-api

A Google Play Store API alternative on fetcher.sh — pay-per-call in USDC via x402, or prepaid credits with a Bearer key, no Google Play Console access. Use when the user wants to search Android apps by keyword with price (free/paid) and country storefront filters, fetch an app's full details, reviews sorted by newest/rating/helpfulness, permissions, or data safety disclosure, list apps similar to a given app, or fetch a developer's app catalog. Also covers Android app store optimization (ASO) research, competitor app monitoring, review sentiment input, and app discovery without Google Play Console developer access.

io.clawhub.michaelmonetized/senior-dev

生产级开发工作流：TODO 跟踪、Graphite PR、GitHub issue、Vercel 部署检查与短信通知。在开始新任务、修 bug、实现功能，或任何需要跟踪进度与代码评审的开发工作时使用。

io.clawhub.itsnishi/audit-code

面向安全的代码审查，聚焦硬编码密钥、危险调用与常见漏洞。

io.clawhub.steipete/swiftui-performance-audit

从代码评审与架构角度审计并改善 SwiftUI 运行时性能。用于诊断 SwiftUI 应用的渲染缓慢、滚动卡顿、CPU/内存占用高、视图过度刷新、布局抖动等问题；当仅靠代码检查不足时，给出用户自行使用 Instruments 分析的指导。

io.clawhub.fetcher-sh/reddit-api

A Reddit API alternative on fetcher.sh — pay-per-call in USDC via x402, or prepaid credits with a Bearer key, no OAuth app registration. Use when the user wants to search Reddit posts across every subreddit by keyword and sort by top, hot, new, or most-discussed, search subreddits or users by keyword, fetch a subreddit's info or its hot/new/top post feed, fetch a single post with its comment tree and comment replies, pull the sitewide best/hot/new/top feeds, or fetch a user's profile, posts, and comments. Also covers Reddit sentiment analysis input, subreddit monitoring, keyword tracking, and Reddit data pipelines without Reddit's own API app registration or rate-limit tiers.

io.clawhub.jdrhyne/munger-observer

用有边界的证据、反面证据、备选方案、机会成本以及可验证的下一步检查，来审视某个具体决策、计划或产出。适用于“Munger 审视”、决策复盘、事前验尸或盲点检查。不会主动扫描历史记录，也不评估某个人的品性、意图或心理状态。

io.clawhub.arthurnie/academic-search

在 arXiv、Google Scholar 与 Semantic Scholar 中进行系统化检索，找出、分析并总结最相关的前 5 篇学术论文。

io.clawhub.buddhasource/github-mcp

GitHub MCP 服务器：让 AI Agent 通过 API 管理仓库、读取/更新文件、处理 issue/PR、分支，并自动化 GitHub 工作流。

io.clawhub.anikgnr/task-development-workflow

TDD 优先的开发工作流，包含结构化规划、任务跟踪与基于 PR 的代码评审。适用于需要澄清需求的软件开发项目。

io.clawhub.itsflow/weekly-synthesis

对一周的工作与思考创建全面综合的复盘总结。

io.clawhub.ishaan-jaff/litellm

通过 LiteLLM 的统一 API 调用 100 多家 LLM 服务商。当你需要调用与主力模型不同的模型时使用（例如在 Claude 上跑任务时用 GPT-4 做代码审查）、对比多个模型的输出、把简单任务路由到更便宜的模型，或访问你的运行环境原生不支持的模型。

io.clawhub.gongyu0918-debug/skill-usefulness-audit

审视你已安装的智能体技能：哪些真正在用、哪些彼此重叠、哪些可能已不值得保留。

io.clawhub.larsderidder/obsidian-tasks

搭建并管理基于看板（Kanban）+ Dataview 的 Obsidian 任务板。创建 Tasks/Board.md 流水线（Backlog/Todo/In Progress/Review/Done）、为每个任务生成带 YAML frontmatter（status/priority/category/due）的笔记，并通过 Dataview 查询生成看板。用于任务跟踪、在列之间移动卡片、保持看板与 frontmatter 同步，以及把任务关联到支撑笔记与研究资料。

io.clawhub.amangarg1999/ai-compound-1-0-1

让你的 AI Agent 自动学习和改进。复盘会话、提炼经验、更新记忆文件，让知识随时间复利积累。可搭建每晚复盘循环，让 Agent 每天更聪明一点。

io.github.affaan-m/ECC/orch-pipeline

orch-* skill 家族共用的编排引擎。定义带门槛的“调研-规划-TDD-评审-提交”流水线、规模分类器、代理映射，以及两个由 orch-* 操作 skill 委派使用的人工关口。通常不直接调用；当某个 orch-* skill 委派其带门槛的调研-规划-TDD-评审-提交流水线时生效。

io.github.getsentry/sentry/sentry-javascript-bugs

依据真实生产问题提炼的缺陷模式，审查 Sentry React 与 TypeScript 改动。在审查前端 diff 或 PR、核对 Warden 发现、审计当前分支、复核生产错误模式，或在 `static/` 中查找常见回归时使用。

io.github.joe-bell/cva/writing-guidelines

按写作指南审查或撰写文档/文案。当被要求“审查我的文档”“检查写作风格”“审计文案”“评审文档语气语调”“对照写作手册检查此页”时使用——并在编写或编辑 docs/src/content/docs/ 下的内容时主动应用，这是本仓库的默认文档风格。

io.github.nexu-io/open-design/writing-guidelines

审查文档是否符合 Writing Guidelines。当被要求“review my docs”“check writing style”“audit prose”“review docs voice and tone”或“check this page against the writing handbook”时使用。

io.github.static-web-server/static-web-server/security

为 Static Web Server（SWS）项目评审或实现安全措施——路径穿越防护、TLS、安全响应头、CORS 与输入校验。

io.github.mono/SkiaSharp/security-audit

审计 SkiaSharp 原生依赖的安全漏洞与 CVE，包括 SkiaSharp-Native 与 SkiaSharp Azure DevOps 流水线的 Component Governance（CG）告警。只读调查，输出带建议的状态报告。当用户要求：审计安全问题或 CVE、检查各依赖的 CVE 状态、寻找安全问题及其 PR 覆盖、汇总未修复漏洞、查看待处理的安全工作、检查 Component Governance 告警、评审原生构建流水线的 CG 告警时使用。触发语：“security audit”“audit CVEs”“CVE status”“what security issues are open”“check vulnerability status”“security overview”“what CVEs need fixing”“CG alerts”“component governance”“check container CVEs”。本技能为只读。要实际修复问题，请使用 `native-dependency-update` 技能。

io.github.forcedotcom/sf-skills/mobile-platform-offline-validate

审查 Lightning Web Component 的移动端离线兼容性——即 Komaci 离线静态分析器，为 Salesforce Mobile App Plus 与 Field Service Mobile App 预填充数据图谱。输出带代码级修复建议的问题清单，涵盖 @wire 配置中的内联 GraphQL 查询、新版 lwc:if / lwc:elseif / lwc:else 指令，以及 Komaci ESLint 规则违规（私有 wire 属性、非局部响应式引用、getter 副作用）。当用户要求“mobile offline review”“Komaci check”“offline priming audit”“offline priming failure”“offline data graph error”，或要求按 @salesforce/eslint-plugin-lwc-graph-analyzer 推荐规则集校验 LWC 时使用。通用 LWC 代码审查（请用相应领域审查技能）或构建带原生移动能力的 LWC（请用 mobile-platform-native-capabilities-integrate）不要使用。