Skip to content
Back to skills

Gpt Import

ASecurity

Import and distill leaked GPT prompts from linexjlin/GPTs into agent knowledge files. Fetches directly from GitHub, distills domain knowledge via agent-refine-knowledge, logs source to claude-secrets catalog.

  • 3 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 27, 2026
data-aigobashgitapi

Works with

  • api

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned May 27, 2026

npx -y skills add SkyWalker2506/claude-config --skill gpt-import --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Gpt Import?

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

Security grade badge for Gpt Import
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/skywalker2506-gpt-import/badge)](https://www.skillsdirectory.com/skills/skywalker2506-gpt-import)

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: gpt-import
description: Import and distill leaked GPT prompts from linexjlin/GPTs into agent knowledge files. Fetches directly from GitHub, distills domain knowledge via agent-refine-knowledge, logs source to claude-secrets catalog.
invocation: /gpt-import
argument-hint: "<agent-id> [--gpt=<gpt-name>] [--search=<query>]"
---

# /gpt-import — GPT Knowledge Importer

## Usage
/gpt-import <agent-id>
/gpt-import <agent-id> --gpt=logo-creator
/gpt-import <agent-id> --search=seo

## What this skill does

Fetches leaked custom GPT instructions from `linexjlin/GPTs` GitHub repo and distills
the domain knowledge into the agent's knowledge/ directory.

## Execution steps

1. **Resolve agent** — Find agent by ID or name in `~/Projects/claude-config/config/agent-registry.json`.
   Get agent's category and capabilities.

2. **Browse available GPTs** — Fetch file list from GitHub API:
   ```bash
   gh api repos/linexjlin/GPTs/contents/prompts --jq '.[].name' 2>/dev/null
   ```
   If `--gpt=<name>` specified: fetch that specific file directly.
   If `--search=<query>`: filter list by query, show top 10 matches to user.
   Otherwise: show list filtered by agent's category keywords, ask user to pick.

3. **Fetch selected GPT content**:
   ```bash
   gh api repos/linexjlin/GPTs/contents/prompts/<filename> --jq '.content' | base64 -d
   ```

4. **Distill** — Call `/agent-refine-knowledge` skill with:
   - Agent ID
   - The fetched GPT content as additional source material
   - Instruction: "Extract only domain knowledge and methodology. Remove all OpenAI/GPT-specific instructions, tool calls, DALL-E references, tone/personality, and proprietary integrations. Output as model-agnostic knowledge topic."

5. **Write to knowledge/** — The refine skill writes to agent's knowledge/ dir.

6. **Log to sources catalog** — Append entry to `~/Projects/claude-secrets/sources-catalog.md`
   (or wherever it was created):
   ```
   | <date> | <agent-id> | <gpt-name> | https://github.com/linexjlin/GPTs/blob/main/prompts/<filename> | distilled |
   ```

7. **Report** — Show user: agent updated, which GPT was source, what topic was added to knowledge/.

## Rules
- Never store raw GPT content in knowledge files
- Never add OpenAI/GPT-specific instructions to agent files
- Always log source to catalog (even if distill quality is low)
- If GPT content is mostly roleplay/personality with no domain knowledge → report "low value, skipped"

Files in this skill

  • README.md831 B
  • SKILL.md2.4 KB
  • plugin.json406 B

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.