connector-librarian
Audits app connectivity, tracing flows to ensure all features are reachable and functional.
Install
mkdir -p .claude/skills/connector-librarian && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18811" && unzip -o skill.zip -d .claude/skills/connector-librarian && rm skill.zipInstalls to .claude/skills/connector-librarian
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Alias wrapper for the Connector Librarian. Use when auditing whether an app is fully wired — every user type has complete flows, every screen is reachable, every route has a backend, no dead code exists. Distinct from code audit (quality) and flow design (UX). Activate when user mentions connectivity, dead code, hanging features, completeness, or asks "is this actually done?"Key capabilities
- →Map user types and their capabilities
- →Trace flows from frontend to database
- →Audit routes for backend coverage
- →Check profile integrity
- →Find dead or orphaned code
- →Output results in TLDR tables with priority levels
How it works
The skill maps user types and traces flows from the frontend through the API and database to the UI. It audits routes for backend coverage and checks profile integrity.
Inputs & outputs
When to use connector-librarian
- →Verify feature connectivity
- →Check flow completeness
- →Find dead code
About this skill
Connector Librarian
This is an alias wrapper. Read the full librarian file for instructions:
/Users/franklawrencejr./Downloads/skills-library-v2 2/librarians/connector-librarian.md
When to Activate
- User asks "is everything connected?" or "is this actually done?"
- User wants to verify all user types work end-to-end
- User mentions dead code, hanging features, or incomplete flows
- Before production launch (complements exit gate)
- User says "connector" or "code connector"
- User asks if all profiles / user types are functional
What This Does
- Maps all user types and what each should be able to do
- Traces every flow: frontend -> API -> database -> response -> UI
- Audits every route for backend coverage
- Checks profile integrity (demo profiles that work like real users)
- Maps feature connectivity graph (does feature A feed feature B?)
- Verifies decision trees (every conditional branch resolves)
- Finds dead/orphaned code
- Outputs everything as TLDR tables with priority levels
When not to use it
- →When performing a code audit for quality
- →When designing user flows for UX
Limitations
- →Distinct from code audit (quality)
- →Distinct from flow design (UX)
How it compares
This skill provides a structured audit of application connectivity and code completeness, unlike manual checks that may miss dead code or incomplete flows.
Compared to similar skills
connector-librarian side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| connector-librarian (this skill) | 0 | 16d | No flags | Intermediate |
| error-handling-patterns | 35 | 2mo | No flags | Intermediate |
| codebase-context-extractor | 4 | 9mo | Review | Intermediate |
| investigating-code-patterns | 1 | 8mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by frvnkfrmchicago
View all by frvnkfrmchicago →You might also like
error-handling-patterns
wshobson
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
codebase-context-extractor
lofcz
This skill provides a comprehensive context extraction system for large codebases. It intelligently analyzes code structure, dependencies, and relationships to extract relevant context for understanding, debugging, or modifying code.
investigating-code-patterns
CaptainCrouton89
Systematically trace code flows, locate implementations, diagnose performance issues, and map system architecture. Use when understanding how existing systems work, researching concepts, exploring code structure, or answering "how/where/why is X implemented?" questions.
investigate
MadAppGang
Unified entry point for code investigation. Auto-routes to specialized detective based on query keywords. Use when investigation type is unclear or for general exploration.
codex-review
rymetry
|
claude
yuiseki
|