software-engineer-connector-manager

Manage local Python connectors with templates and environment-variable declarations.

1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/MightyHive/ingestion-agent --skill software-engineer-connector-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: software-engineer-connector-manager
Source: https://github.com/MightyHive/ingestion-agent/tree/main/src/skills/software-engineer-connector-manager
Command: npx skills add https://github.com/MightyHive/ingestion-agent --skill software-engineer-connector-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes the management of a local Python connector library, enabling consistent templates, safe environment-variable declarations, and a clear handoff to DevOps or API researchers without cloud deployment.

Core Features & Use Cases

  • Read and inspect existing connectors.
  • Create or update connectors based on approved templates.
  • Declare environment variable names for secrets without embedding values; ensure runtime configuration.
  • Generate source code scaffolds with a fetch(params, context) pattern and a predictable file layout for the library.

Quick Start

Create or update a local connector using the provided templates, and ensure environment variable names are declared but not hardcoded.

Frequently Asked Questions about software-engineer-connector-manager

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

FAQPage Schema
How do I manage a local Python connector library without cloud deployment?

Managing a local Python connector library involves automating connector listing, reading, creating, and updating using standardized templates. This approach enforces a fetch(params, context) contract and safe environment-variable declarations without requiring cloud deployment.

How do I safely declare environment variables for Python API connectors?

Safely declare environment variables by using os.getenv names within your connector code to reference secrets. This practice ensures runtime configuration is validated and persisted without embedding sensitive values directly in the local library source code.

What is the standard code pattern for generating Python connector templates?

The standard code pattern for Python connector templates is the fetch(params, context) contract. This enforces a predictable file layout, validates generated code, and standardizes how connectors receive parameters and runtime context.

Can I update existing Python connectors using approved templates?

Yes, you can update existing Python connectors by reading and inspecting them against approved templates. The process validates the code, ensures required environment variables are declared via os.getenv, and persists the changes to the local library.

Do I need cloud deployment to coordinate API research with local Python connectors?

No, you do not need cloud deployment to coordinate API research with local Python connectors. The management process standardizes templates, validates the fetch(params, context) contract, and persists changes directly to a local library for safe DevOps handoff.