Skip to content

suboss87/FDEOps / skills/connect

connect

Verified

Configure or diagnose access to a requested source using available host tools. Use for source MCP setup; source configuration needs no engagement record and credentials stay with the host.

FileKindSize
.fde-generated.jsonconfig749 B
SKILL.mdskill md1.4 KB
agents/openai.yamlconfig222 B
references/connect.mdmarkdown1.6 KB
references/debrief.mdmarkdown13.7 KB
references/ingest.mdmarkdown6.2 KB
references/source-setup.mdmarkdown2.8 KB
references/task-context.mdmarkdown6.6 KB

references/connect.md

View on GitHub
# connect - Connect a source

**Enter when:** the user asks to connect a notes, chat or document source, or an expected source cannot be read.

Apply [task context](task-context.md). Source setup can run independently of a customer record. Follow [source setup](source-setup.md) for permitted tools, credentials, connectivity checks and export alternatives.

## Method

1. Identify the source and the material the user wants to read. Inspect the host's actual available tools before recommending setup.
2. If the source already works, use a narrowly scoped requested read. Do not install another connector.
3. If setup is needed, verify current provider and host documentation, explain the required access, and make only authorized configuration changes. Never put credentials into prompts or customer records.
4. Test the selected source and distinguish configuration from successful retrieval. If access is blocked, report the specific limitation and an available file or paste alternative.
5. If the user also wants to update a customer record, continue with [ingest](ingest.md) after selecting that record. Otherwise stop after the requested setup or read.

## Checkpoint

Return what is connected, what read was verified, any access gap, and how to request the next pull. Do not claim an integration works from configuration alone or write customer records during setup.

## Principles

- Existing source tools first; configuration only when needed.
- Minimum requested read, no ambient synchronization.
- Credentials stay in supported secret storage.
- Record updates require their own review and confirmation.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall