spk-team-connectors

Route Spec Kitty connector work across tracker, sync, SaaS, and external services.

1.6k|156|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/Priivacy-ai/spec-kitty --skill spk-team-connectors
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spk-team-connectors
Source: https://github.com/Priivacy-ai/spec-kitty/tree/main/src/charter/offering/skills/spk-team-connectors
Command: npx skills add https://github.com/Priivacy-ai/spec-kitty --skill spk-team-connectors

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Connector and integration work in Spec Kitty projects often gets mixed into mission specs or handled without clear ownership, causing configuration drift and unclear data-flow boundaries. This Skill provides a consistent operating procedure for identifying connectors, routing work to the right service, and keeping integration configuration out of mission specs.

Core Features & Use Cases

  • Connector Identification: Determine which connector and owning service a piece of integration work belongs to before making changes.
  • Data-Flow Routing: Confirm whether data flows through the tracker, sync layer, SaaS platform, or an external API, and delegate to the appropriate companion skills (spk-team-auth, spk-team-sync, spk-team-tracker).
  • Spec Hygiene: Keep connector configuration out of mission specs unless it changes product behavior.
  • Use Case: When a task involves syncing Spec Kitty work-package state with a hosted tracker, use this Skill to classify the work as tracker-bound, pull credentials via the auth skill, and route state changes through the tracker skill instead of editing mission artifacts directly.

Quick Start

Use the spk-team-connectors skill to route this integration task involving tracker sync to the correct owning service and companion skills.

Frequently Asked Questions about spk-team-connectors

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

FAQPage Schema
How do I handle connector integration work in Spec Kitty?

Identify the connector and its owning service first, then confirm whether data flows through the tracker, sync layer, SaaS platform, or an external API. Delegate credentials to the auth skill, transport to the sync skill, and tracker-bound state to the tracker skill.

Should connector configuration go into Spec Kitty mission specs?

No, connector configuration should stay out of mission specs unless it changes product behavior. Connector work is treated as integration operations, not generic mission authoring, so operational settings live with the owning service.

Which skills work with spk-team-connectors for integrations?

Three companion skills handle specific concerns: spk-team-auth manages credentials, spk-team-sync handles sync transport, and spk-team-tracker manages tracker-bound state. The connectors skill routes work to the appropriate one.

When should I not use the connectors skill in Spec Kitty?

Do not use it for generic mission authoring or spec writing that has no external integration component. It is scoped to integration operations involving external services, sync, or tracker connectivity, not core spec-driven development tasks.