agentleFS
Sign inStart free
GabrielaStarkGabrielaStark/SDD/.claude/skills/onboarding/SKILL.md

onboarding

Skill1 starsChanged 5 months agoMITView on GitHub

Protocolo de reconocimiento para proyectos heredados o de mantenimiento. Genera CLAUDE.md y BIG_PICTURE.md con análisis completo del estado actual del proyecto.

  • Reads credentials

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 82 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Sé específico: No digas "usa una base de datos" — di "PostgreSQL 15 vía Prisma ORM".

    line 81

“Common” is measured: kept by at least 6 in 10 of the 82 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Reconocimiento de Proyecto — Protocolo de Onboarding

Contexto

Este es un proyecto existente que voy a mantener. No lo construí yo. Necesito entender el estado actual antes de hacer cambios. Analiza el proyecto completo como si fueras un ingeniero senior que acaba de heredar este código.

Instrucciones

Fase 1: Exploración

  1. Recorre toda la estructura de carpetas del proyecto
  2. Identifica el stack tecnológico (lenguajes, frameworks, bases de datos, herramientas de build)
  3. Lee los archivos de configuración clave: package.json, pom.xml, build.gradle, requirements.txt, Dockerfile, docker-compose.yml, .env.example, CI/CD configs, etc.
  4. Identifica puntos de entrada principales (main, index, app, bootstrap)
  5. Revisa si existen tests y qué tipo (unitarios, integración, E2E)
  6. Busca documentación existente (README, docs/, wiki, comentarios relevantes)

Fase 2: Genera CLAUDE.md

Crea el archivo CLAUDE.md en la raíz del proyecto con las siguientes secciones:

# CLAUDE.md — [Nombre del Proyecto]

## Stack Tecnológico
<!-- Lenguajes, frameworks, librerías principales, versiones detectadas -->

## Estructura del Proyecto
<!-- Árbol de carpetas explicado. No solo listar: explicar qué hace cada carpeta principal -->

## Comandos Esenciales
<!-- Cómo instalar dependencias, compilar, correr, testear, lint, build para producción -->

## Dependencias Principales
<!-- Las dependencias más importantes y para qué se usan. No listar todas, solo las que importan -->

## Convenciones de Código
<!-- Patrones detectados: naming, estructura de archivos, manejo de errores, estilo de imports, arquitectura -->

## Configuración del Entorno
<!-- Variables de entorno necesarias, archivos de config, requisitos del sistema -->

Fase 3: Genera BIG_PICTURE.md

Crea el archivo BIG_PICTURE.md en la raíz del proyecto con las siguientes secciones:

# BIG_PICTURE.md — [Nombre del Proyecto]

## Diagrama de Arquitectura
<!-- Diagrama en texto (ASCII o Mermaid) mostrando componentes principales y cómo se conectan -->

## Flujo de Datos
<!-- Cómo fluye la información: desde la entrada del usuario hasta la base de datos y de vuelta -->

## Puntos de Entrada
<!-- Archivos y funciones donde arranca la ejecución. Rutas principales si es web. -->

## Módulos y Responsabilidades
<!-- Cada módulo/paquete principal: qué hace, de qué depende, quién lo consume -->

## Estado de Tests
<!-- Cobertura actual, tipos de test encontrados, qué está testeado y qué no -->

## Deuda Técnica y Riesgos
<!-- Dependencias desactualizadas, código duplicado, patrones inconsistentes, vulnerabilidades potenciales, TODOs/FIXMEs encontrados, archivos sin tests -->

## Observaciones del Ingeniero
<!-- Tu criterio profesional: qué te preocupa, qué está bien hecho, por dónde empezarías a mejorar -->

Reglas

  • No asumas nada. Lee los archivos antes de concluir.
  • Sé específico. No digas "usa una base de datos" — di "PostgreSQL 15 vía Prisma ORM".
  • Señala riesgos reales. Si hay dependencias con CVEs conocidos, archivos de 500+ líneas sin tests, o patrones que huelen mal, dilo directo.
  • Si algo no existe, dilo. Si no hay tests, no hay docs, no hay CI — eso es un hallazgo, no algo que omitir.
  • Los diagramas en Mermaid son preferidos sobre ASCII cuando sea posible.

Download now (ZIP)

  • Other versions94 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 1

    1. GabrielaStark/stark★ 170% same

    Wrote their own version · 93

    1. coreyhaines31/marketingskills★ 58ksame name
    2. anthropics/knowledge-work-plugins★ 34ksame name
    3. actions/runner-images★ 14ksame name
    4. BuilderIO/agent-native★ 7.6ksame name
    5. gnekt/My-Brain-Is-Full-Crew★ 3.9ksame name
    6. ColeMurray/background-agents★ 3.4ksame name
    7. huytieu/COG-second-brain★ 1.3ksame name
    8. openai/mcp-extensions★ 1.1ksame name
    9. Nexus-JPF/note-companion★ 874same name
    10. elevenlabs/skills★ 527same name

    83 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use paywalls, popups and 10 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • CesarjoquinSkill

      paywalls

      When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.

      Also in 19 projects that use this

    • CesarjoquinSkill

      popups

      When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.

      Also in 18 projects that use this

    • coreyhaines31Skill

      marketing-council

      When the user wants multiple expert perspectives on a marketing question — a simulated board of advisors staffed by legendary marketers (Seth Godin, David Ogilvy, Eugene Schwartz, April Dunford, Rory Sutherland, Alex Hormozi, Byron Sharp, and more). Also use when the user mentions 'marketing council,' 'board of advisors,' 'advisory board,' 'what would Seth Godin say,' 'what would Ogilvy think,' 'channel Hormozi,' 'get multiple perspectives,' 'debate this,' 'have the council review,' 'marketing mentors,' or asks how a famous marketer would approach their problem. The council gives each advisor's take through their documented frameworks, surfaces where they disagree, and synthesizes a recommendation. For executing the winning direction, hand off to positioning, offers, copywriting, ads, or the relevant skill.

      Also in 13 projects that use this

    • roerohanSkill

      prospecting

      When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses. Also use when the user mentions "prospecting," "build a prospect list," "find prospects," "find leads," "lead gen list," "find SaaS companies that," "find B2B companies," "find local businesses," "ICP-fit accounts," "who should we go after," "outbound list," "target account list," "find clients near me," "businesses without websites," "prospect research," "qualified leads," "find my first customers," "early adopters," "design partners," "beta users," or "who has this problem." Use this for the list-building and qualification phase. For writing the outbound copy after the list is built, see cold-email. For deep competitive research on specific accounts, see competitor-profiling.

      Also in 16 projects that use this

    • roerohanSkill

      emails

      When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.

      Also in 18 projects that use this

    • +7 more from Cesarjoquin
  • In this repository8 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free