Use this skill when the user wants to convert a REDCap training outline (uploaded as a Word document) into a RAG-optimized Knowledge Base article in the RC-KB format. Triggers include: uploading a training outline .docx, asking to "convert this outline", "build a KB article", "turn this into a KB article", or any request to produce a new RC-[DOMAIN]-[NN] article from source material. Also trigger when the user says things like "let's do the next outline" or "here's the next one". Do NOT trigger for editing or refining existing articles — use the redcap-kb-refiner skill for that.
Use this skill whenever the user wants to update, correct, revise, or add to existing REDCap KB articles, or when new source material (a Word document, a text description, a correction) arrives that may need to go into the knowledge base. Triggers include uploading a new .docx or text with updated REDCap content, saying "update the article about X", "add this to the KB", "this article is wrong/outdated", "REDCap changed how X works", "add a Q&A about Y", "there is a new feature in REDCap". Also trigger when the user says things like "here is new info" or "this needs to be in the KB" without specifying a specific article. Use this skill even if you are not sure whether the content maps to an existing article — the skill handles that assessment. Do NOT use this skill to create a brand-new article from a training outline from scratch — use the redcap-kb-builder skill for that.
Build a new REDCap Data Dictionary CSV from scratch, or add new instruments and fields to an existing one. Use this skill whenever a user wants to create REDCap instruments, design a data dictionary from a study protocol or codebook, convert a CRF to REDCap format, or extend an existing project with new forms. Trigger on: "build me a data dictionary", "create a DD for my study", "I have a protocol that needs to become a REDCap project", "make a REDCap form for", "add a new instrument to my project", "design these fields in REDCap", "convert this codebook to REDCap", "help me set up my REDCap project variables", "create a data collection form for", "I need to capture these variables in REDCap". Also trigger when the user describes variables, scales, or questionnaires they want to collect and needs them formatted as a REDCap data dictionary. If the user is not sure whether to start fresh or modify an existing DD, use this skill and ask them.
Build the three REDCap longitudinal project CSV files — Arms, Events, and Instrument Designations — from user input or uploaded documentation. Use this skill whenever a user wants to set up or draft a longitudinal project structure, is starting a new longitudinal REDCap project, wants to generate importable CSV files, or describes a study schedule and needs it turned into importable CSVs. Trigger on: "create my events", "set up the longitudinal structure", "generate the arms and events", "build the event mapping", "import longitudinal setup", "I have a protocol and need the event CSVs", "help me design the longitudinal structure", or any time the user describes study timepoints, visit schedules, arms, or form assignments and wants files to import. Also trigger when a user shares a protocol document, schedule table, or spreadsheet and asks to turn it into a REDCap longitudinal setup. This is the companion to the redcap-longitudinal-structure skill (which reads existing files) — use this one when building from
Analyze a REDCap project for design issues, logic errors, and structural problems by connecting to the REDCap API. Use this skill whenever the user wants to audit, review, health-check, or assess a REDCap project's structure and configuration. Trigger on: "analyze my REDCap project", "audit this project", "review the project design", "check for issues in my REDCap project", "is my project structured correctly", "project health check", "look at my REDCap project", "can you review how this project is set up", "something seems wrong with my project structure", or any time the user wants an automated review of a REDCap project through the API. Walks the user step by step through obtaining an API token if they don't have one, confirms the correct REDCap instance before pulling data, and produces a structured report of findings.
Search the REDCap knowledge base (kb/ in the REDCap_KB_RAG repo) to find and read relevant articles for any topic or question. Use this skill whenever you need to look something up in the REDCap KB, answer a question about REDCap functionality, find articles before writing new KB content, or check what the KB already says about a topic. Trigger on phrases like "what does the KB say about", "look up in the KB", "find articles about", "search the knowledgebase", "is there a KB article on", or any time another skill needs to pull in related REDCap documentation before doing its work. When in doubt, use this skill — it's the authoritative source for REDCap knowledge.
Read and interpret a REDCap Codebook PDF or Data Dictionary CSV to produce a structured project overview. Use this skill whenever a user uploads a Codebook PDF or Data Dictionary CSV and wants to understand what a REDCap project collects, get a summary they can share with stakeholders, or provide a complete project description for LLM-assisted analysis. Trigger on: "summarize this project", "what does this project collect", "give me an overview of this REDCap project", "I uploaded a codebook", "read this codebook", "what's in this codebook", "explain this project to me", "help an LLM understand this project", "create a project summary for documentation", or any time a user uploads a file whose name ends in DataDictionary, Codebook, or PDF and asks for a description or summary. Also trigger when another skill needs a full picture of the project before doing its work (e.g. building branching logic, writing KB articles about a specific project). Use --llm-context mode when another skill or pipeline needs the out
Parse and interpret REDCap longitudinal project structure from the three exported CSVs: Arms, Events, and Event-Instrument Mapping (Instrument Designations). Use this skill whenever a user provides any of these files, asks about a project's longitudinal design, wants to know which forms are collected at which events or timepoints, needs to map out arm/event/form relationships, or is troubleshooting branching logic that references events. Trigger on: "longitudinal", "arms", "events CSV", "event mapping", "define my events", "instrument designations", "which forms are at which events", "event-instrument mapping", "unique event name", or when any uploaded CSV has "Arms", "Events", or "Designat" in the filename. Also trigger when the user asks "what events does this project have?" or "which forms are assigned to which events?" even without uploading a file — the answer will require these CSVs and you should ask for them.