openclaw 网盘下载
OpenClaw

技能详情(站内镜像,无评论)

首页 > 技能库 > Context7 API Documentation Fetcher

Fetch up-to-date library documentation via Context7 API. Use PROACTIVELY when: (1) Working with ANY external library (React, Next.js, Supabase, etc.) (2) User asks about library APIs, patterns, or best practices (3) Implementing features that rely on third-party packages (4) D…

开发与 DevOps

许可证:MIT-0

MIT-0 ·免费使用、修改和重新分发。无需归因。

版本:v1.0.0

统计:⭐ 0 · 1.9k · 7 current installs · 7 all-time installs

0

安装量(当前) 7

🛡 VirusTotal :可疑 · OpenClaw :可疑

Package:am-will/context7-api

安全扫描(ClawHub)

  • VirusTotal :可疑
  • OpenClaw :可疑

OpenClaw 评估

The skill largely does what it claims (calls Context7 APIs), but it embeds a default API key in source and fails to declare or document required credentials — a surprising and risky mismatch.

目的

The name/description match the included script: the tool queries context7.com for library docs. However the skill metadata declares no required credentials or env vars while the script expects CONTEXT7_API_KEY (and falls back to a hardcoded key). The missing declaration of the API credential is an incoherence.

说明范围

SKILL.md instructs running the packaged script to search and fetch context; it does not direct reading unrelated local files or other secrets. But the instructions omit any mention of setting CONTEXT7_API_KEY or the presence of a default key, which may cause silent use of the embedded key when run.

安装机制

No install spec; this is an instruction-only skill with a local Python script. No external download/install step is present, which minimizes install-time risk.

证书

The code reads an environment variable CONTEXT7_API_KEY but the skill metadata lists no required env vars or primary credential. Worse, the script embeds a default API key in source — embedding credentials in code is inappropriate and increases risk (key leakage, abuse, or unexpected shared usage).

持久

The skill does not request permanent presence (always:false) and doesn't attempt to modify other skills or system-wide settings. It runs as an on-demand CLI client.

安装(复制给龙虾 AI)

将下方整段复制到龙虾中文库对话中,由龙虾按 SKILL.md 完成安装。

请把本段交给龙虾中文库(龙虾 AI)执行:为本机安装 OpenClaw 技能「Context7 API Documentation Fetcher」。简介:Fetch up-to-date library documentation via Context7 API. Use PROACTIVELY when: …。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装:https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/am-will/context7-api/SKILL.md
(来源:yingzhi8.cn 技能库)

SKILL.md

打开原始 SKILL.md(GitHub raw)

---
name: context7
description: |
  Fetch up-to-date library documentation via Context7 API. Use PROACTIVELY when:
  (1) Working with ANY external library (React, Next.js, Supabase, etc.)
  (2) User asks about library APIs, patterns, or best practices
  (3) Implementing features that rely on third-party packages
  (4) Debugging library-specific issues
  (5) Need current documentation beyond training data cutoff
  Always prefer this over guessing library APIs or using outdated knowledge.
---

# Context7 Documentation Fetcher

Retrieve current library documentation via Context7 API.

## Workflow

### 1. Search for the library

```bash
python3 ~/.claude/skills/context7/scripts/context7.py search "<library-name>"
```

Example:
```bash
python3 ~/.claude/skills/context7/scripts/context7.py search "next.js"
```

Returns library metadata including the `id` field needed for step 2.

### 2. Fetch documentation context

```bash
python3 ~/.claude/skills/context7/scripts/context7.py context "<library-id>" "<query>"
```

Example:
```bash
python3 ~/.claude/skills/context7/scripts/context7.py context "/vercel/next.js" "app router middleware"
```

Options:
- `--type txt|md` - Output format (default: txt)
- `--tokens N` - Limit response tokens

## Quick Reference

| Task | Command |
|------|---------|
| Find React docs | `search "react"` |
| Get React hooks info | `context "/facebook/react" "useEffect cleanup"` |
| Find Supabase | `search "supabase"` |
| Get Supabase auth | `context "/supabase/supabase" "authentication row level security"` |

## When to Use

- Before implementing any library-dependent feature
- When unsure about current API signatures
- For library version-specific behavior
- To verify best practices and patterns