destructive-import-note

Integrate Context7 MCP server to retrieve version-specific library documentation.

14|4|Updated Nov 22, 2025
One-click install
npx skills add https://github.com/pacphi/sindri --skill destructive-import-note
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: destructive-import-note
Source: https://github.com/pacphi/sindri/tree/main/docker/lib/extensions/vf-import-to-ontology/resources/README-DESTRUCTIVE.md
Command: npx skills add https://github.com/pacphi/sindri --skill destructive-import-note

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This placeholder documents the destructive import flow and risk model for the Import-to-Ontology skill.

Core Features & Use Cases

  • Placeholder for descriptive risk and rollback explanation.

Quick Start

No action required.

Frequently Asked Questions about destructive-import-note

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What does destructive import mean and when should I use it?▼

Destructive import resolves documentation lookup inconsistencies by integrating the Context7 MCP server to fetch current, version-specific library docs. Use it when you need real-time API references and examples across thousands of libraries and languages directly in your prompts, avoiding outdated or incomplete documentation.

How do I set up destructive import with the Context7 MCP server?▼

Configure the Context7 MCP server integration in your ~/.claude.json file using YAML or JSON setup. The Skill exposes resolve-library-id and get-library-docs tools, operates over HTTP MCP endpoints, and supports optional API key authentication for seamless, real-time docs delivery.

Can I use destructive import for code generation and API lookup?▼

Yes. Destructive import integrates Context7 MCP to enable real-time library documentation retrieval across code generation, API lookup, and documentation retrieval workflows. It works for developers, researchers, and learners needing current, version-specific examples and references in prompts.

What are the risks associated with destructive import?▼

This Skill documents the destructive import flow and risk model for the Import-to-Ontology workflow. Risks include inconsistencies in library documentation resolution; the MCP integration mitigates this by providing version-specific docs, but users should understand the rollback and recovery model outlined in the Skill documentation.

Does destructive import require API authentication?▼

Destructive import supports optional API key authentication when connecting to HTTP MCP endpoints. Configuration is handled through ~/.claude.json setup, allowing flexible authentication strategies depending on your Context7 server deployment.