integrations-engine

Detect and route to optional external plugins at session start.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/olaTechie/scientific-paper-writer --skill integrations-engine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integrations-engine
Source: https://github.com/olaTechie/scientific-paper-writer/tree/main/skills/integrations
Command: npx skills add https://github.com/olaTechie/scientific-paper-writer --skill integrations-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Enables optional plugin integrations for the scientific-paper-writer without forcing dependencies, letting users extend capabilities only when plugins are present.

Core Features & Use Cases

  • Silent, session-scoped plugin detection at first command invocation to augment the workflow without requiring plugins.
  • Non-intrusive routing to detected plugin SKILL.md advertised capabilities, with built-in fallbacks when plugins are absent.
  • User override controls via PAPER_CONTEXT.md to disable integrations or selectively enable/disable specific integrations.

Quick Start

Configure your environment by creating or editing PAPER_CONTEXT.md to enable or disable integrations, then invoke a Claude writing command to trigger automatic plugin detection.

Frequently Asked Questions about integrations-engine

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

FAQPage Schema
How do I detect optional plugins at session start without forcing dependencies?

Silent plugin detection scans installed plugins for SKILL.md definitions at first command invocation, extending workflows only when plugins are present while applying built-in fallbacks otherwise. This non-intrusive routing caches results for the session.

Can I selectively disable specific integrations in my scientific writing workflow?

You can selectively disable specific integrations by editing PAPER_CONTEXT.md. This user override file allows you to disable integrations entirely or enable and disable specific plugin routes to control your scientific writing environment.

What happens when external plugins are absent during manuscript writing?

When external plugins are absent during manuscript writing, the system applies safe, backwards-compatible built-in fallbacks. Non-intrusive routing ensures the core workflow continues functioning normally without forcing any missing plugin dependencies.

How does plugin routing work with versioned frontmatter and trigger-based discovery?

Plugin routing uses versioned frontmatter in SKILL.md definitions to discover advertised capabilities through trigger-based matching. The engine respects these definitions during session-scoped detection, applying silent routing to matching capabilities while caching results.

Do I need to install plugins to use the Claude Scientific Writer environment?

You do not need to install plugins to use the Claude Scientific Writer environment. Optional plugin integrations augment the core manuscript-writing workflow only when present, with safe fallbacks ensuring full backwards compatibility without forced dependencies.

Why are my plugin integrations not loading after editing PAPER_CONTEXT.md?

Plugin integrations may not load if PAPER_CONTEXT.md overrides disable them or if installed plugins lack valid SKILL.md definitions. Detection occurs silently at first command invocation, so verify your overrides and plugin frontmatter formatting.