What kind of code output should I expect?

The skill is configured to provide minimal, diff-only responses that align with existing patterns to keep the codebase clean and concise.

How does this skill handle NPID authentication?

It mandates the reuse of the shared auth loader in src/session.ts and the local ~/.npid_session.pkl file, prohibiting new session managers or login flows.

How are athlete positions formatted using this skill?

Positions are kept exactly as they come from the API—pipe-separated abbreviations—without manufacturing placeholders like 'NA' for missing data.

Which files does the skill inspect for patterns?

It prioritizes checking the NPID API client, MCP server sessions, the season calculator, and existing Raycast form components before proposing changes.

What is the primary purpose of the npid-existing-code skill?

It ensures developers reuse existing code patterns and authentication logic within the prospect-pipeline repository instead of creating redundant or conflicting abstractions.

NPID Pipeline Implementation Guide

Name: NPID Pipeline Implementation Guide
Author: 23Maestro

by23Maestro

•

Productivity & Workflow

Enforces the reuse of existing Prospect ID patterns and authentication logic to ensure consistency across the prospect pipeline codebase.

About

This skill ensures that development within the prospect-pipeline repository remains consistent by prioritizing existing abstractions over new ones. It guides Claude to utilize established NPID API clients, shared session management, and specific data formatting rules for athlete positions. By strictly following patterns found in Python and TypeScript MCP servers, it prevents the introduction of redundant authentication layers or non-standard data structures, resulting in cleaner, more maintainable code diffs that align with the repository's core design principles.

Key Features

1 GitHub stars
Reuses existing NPID session management via ~/.npid_session.pkl
Prioritizes established API client patterns over new abstractions
Prevents redundant authentication flows and placeholder data manufacturing
Enforces standard API-driven data formatting for player positions
Minimizes code footprint by aligning with existing repository structures

Use Cases

Extending NPID search functionality within the Raycast extension
Refactoring MCP servers to use shared authentication utilities
Adding new athlete data fields while maintaining API-consistent formatting

About

Key Features

1 GitHub stars
Reuses existing NPID session management via ~/.npid_session.pkl
Prioritizes established API client patterns over new abstractions
Prevents redundant authentication flows and placeholder data manufacturing
Enforces standard API-driven data formatting for player positions
Minimizes code footprint by aligning with existing repository structures

Use Cases

Extending NPID search functionality within the Raycast extension
Refactoring MCP servers to use shared authentication utilities
Adding new athlete data fields while maintaining API-consistent formatting