From raylu
Use when the user wants to set up a recurring, automated sourcing routine that discovers new companies on a schedule — defining an investment thesis, inspiration sources, a scoring threshold and exclusions, an outreach strategy, and a cadence. Trigger phrases include 'set up a sourcing routine', 'automatically find new companies every week', and 'build a recurring deal-sourcing pipeline'.
How this skill is triggered — by the user, by Claude, or both
Slash command
/raylu:sourcingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Walk through these steps ONE AT A TIME with the user. Do not skip steps.
Walk through these steps ONE AT A TIME with the user. Do not skip steps.
Ask: "What space are you focused on? Describe the types of companies you're looking for." From their answer, derive: category, description, subcategories, regions. Check list_market_maps for existing maps — ask if they want to use one or create new. Ask about firmographic preferences: headcount range, funding stage, geography.
Ask: "Where should I look for new company leads each time this runs?" Options:
Ask: "How do you evaluate whether a company is worth sourcing?" Check if they have a scoring definition in Raylu. Ask: minimum score threshold (default 60), exclude CRM companies (default yes), exclude companies with existing campaigns (default yes).
Call generate_campaign without a strategyId — this returns available strategies. Present the options and let the user pick. Ask: should campaigns auto-start or stay as drafts?
Ask: "How often should this run?" (daily, every Monday, weekly, biweekly) After collecting all choices, help the user create a scheduled task with the filled-in pipeline prompt.
The recurring run should:
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub raylu-dev/raylu-plugins --plugin raylu