Skip to content
Back to skills

Source Check

ASecurity

Use to fetch current documentation for technical topics like APIs, libraries, or tools mentioned in conversation.

  • 87 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 5, 2026
toolsreactnodenodejsapidocumentation

Works with

  • cli
  • api

Security analysis

A100/100

Scanned September 22, 2026

npx -y skills add denolfe/dotfiles --skill source-check --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Source Check?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Source Check
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/denolfe-source-check/badge)](https://www.skillsdirectory.com/skills/denolfe-source-check)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: source-check
description: Use to fetch current documentation for technical topics like APIs, libraries, or tools mentioned in conversation.
disable-model-invocation: true
---

# Source Check

Fetch current documentation for technical topics in context.

## Invocation

- `/source-check` — fetch docs for technical topics in recent conversation
- `/source-check [topic]` — fetch docs for a specific topic

## Scope

Fetch current info for:
- Libraries and frameworks in use
- APIs and their current behavior
- Tools, CLIs, and their options
- Version-specific features or changes

Skip: conceptual discussions, architecture questions, opinion-based topics.

## Pipeline

### Step 1: Identify Topics

Scan recent conversation for technical topics that would benefit from current documentation. Prioritize:
1. Libraries/frameworks being discussed
2. APIs or methods in use
3. Tools, CLIs, configuration options
4. Version-specific behavior

List each topic as a brief phrase.

### Step 2: Fetch via Subagent

Dispatch a general-purpose subagent with:

```
Fetch current documentation for these technical topics:

1. [topic 1]
2. [topic 2]
...

For each topic:
1. Generate 1-2 targeted search queries (include library name, version if relevant)
2. Search the web for current docs (prefer official docs, changelogs, release notes)
3. If needed, fetch the official docs URL for details
4. Summarize current state/behavior

Return ONLY this format:

## Current Documentation

### [Topic 1]
[Current state/behavior summary - 2-3 sentences]

Source: [Official Docs](url)

### [Topic 2]
[Current state/behavior summary - 2-3 sentences]

Source: [Changelog](url)

If a topic has changed recently, note what changed.
```

### Step 3: Integrate

Present subagent results. Use fetched documentation to inform subsequent responses.

## Output Format

```markdown
## Current Documentation

### [Topic]
[Current state/behavior summary]

Source: [Source Name](url)

### Notable Changes
- [Recent change if relevant]
```

Omit Notable Changes if nothing recent.

If no technical topics found:
> No technical topics identified in recent context.

## Examples

**Single topic:**

### React useEffect
Runs after render by default. Cleanup function runs before next effect and on unmount. Dependencies array controls when effect re-runs.

Source: [React Docs](https://react.dev/reference/react/useEffect)

**Multiple topics with changes:**

### Node.js 20 ESM Support
Native ESM fully supported. Use `"type": "module"` in package.json or `.mjs` extension. `require()` still works in CommonJS files.

Source: [Node.js Docs](https://nodejs.org/api/esm.html)

### Notable Changes
- Node 20 added `require()` of ESM modules behind flag (--experimental-require-module)

## After Output

Resume normal conversation. Use fetched documentation to inform subsequent responses.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.