strict-api
仓库创建 2025年10月19日最近提交 9 天前SkillHot 收录 4 小时前
▸ 精选理由
有效降低因代理发明不存在接口导致的运行时错误,适合依赖既有代码库的场景。
▸ 风险提示
需要读取项目依赖或源码以做校验,可能要求较高的环境访问权限。
这个 Skill 做什么
在生成或调用代码前验证方法、导入和变量在目标环境中确实存在,防止虚构 API。
在写代码或调用前先验证目标环境里那些方法、导入和变量确实存在,杜绝凭想象“造”API。适合版本差异敏感或有人强调“别幻想函数/请验真”的场景,能避免运行时报找不到函数的尴尬。特点是基于可证实的事实才用,减少因为假设而引入的调试成本。
▸ 展开 SKILL.md 英文原文
Use when the user says 'no hallucinations', 'verify APIs', 'reality check', or 'don't invent functions'. Prevents the agent from calling methods, imports, or variables that do not provably exist in the user's installed version.
2.3w
Stars
3.2k
Forks
40
仓库内 Skill
+2.2k
7 日增星
安装 / 使用
给你的 Agent 一句话(通用)
帮我安装这个 skill:https://raw.githubusercontent.com/alirezarezvani/claude-skills/main/engineering/strict-api/SKILL.md或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/alirezarezvani/claude-skills/main/engineering/strict-api/SKILL.md"SKILL.MD 节选查看完整文件 ↗
# Strict API Verification Inventing a function that doesn't exist is the opposite of efficiency. You wrote a line that looks minimal. You shipped a bug that takes an hour to debug. The true minimal path is: use only what is provably there. ## Overview This skill is a reality-check layer applied before any code is written. It is not about being slow — it is about being correct the first time. Use it alongside `minimalist` when the user wants both less code and verified code. ## The Only Rule Before you write any function call, import, or method access, you must be able to answer: **"Does this exist in the version the user is running?"** If the answer is "probably" or "I think so" — **s
via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有