# La Week Signal > Use when you need recurring Los Angeles week signal for COPS scenario design, weekly openings, roll call setup, side-lane inspiration, or city-pressure research. Resolve a date anchor, pull cyclical LA city patterns for that week or season, and translate them into believable police consequences. - Skill: `ludofleury/la-week-signal` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add ludofleury/la-week-signal` - Raw SKILL.md: https://api.skillmd.com/api/skills/ludofleury/la-week-signal/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Research & Search - Author: ludofleury (https://skillmd.com/u/ludofleury) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/ludofleury/la-week-signal --- # LA Week Signal This skill retrieves and translates Los Angeles week pressure for COPS campaign design. Its job is not to write the final scene. Its job is to tell us what the city is doing, what that means for police work, and what side pressure or connected material becomes plausible that week. For far-future campaign play, it should prioritize cyclical, seasonal, and calendar-based Los Angeles patterns that can still plausibly exist in 2030, 2032, or 2033. ## When to use Use this skill when the user asks for any of: - what could be happening in Los Angeles at a given time of year - week setup for a scenario - real events for a `LAPD Blues` or `roll call` - side-lane inspiration around a date - COPS Channel style week pressure - city-first scenario inspiration - actual or cyclical LA events, history, schedules, or civic pressure that can feed the campaign ## What this skill is for This skill should: - resolve a usable date anchor - pull cyclical Los Angeles week signal - establish the seasonal and weather context in broad strokes - filter for police relevance - translate city activity into police consequences - suggest credible side and connected lanes - provide usable inputs for later skills such as scenario shaping or roll call writing This skill should not: - choose the main scenario lane by default - replace the GM's core design work - write the final `LAPD Blues` or `roll call` - turn every event into a giant crisis - depend on one-off headlines that cannot be projected into a near-future campaign - default to scandals, political explosions, or breaking news unless the user explicitly wants that inspiration mode - pretend to know hyper-precise weather if the exact day is not the point ## Required input This skill needs a usable date anchor. Accepted forms: - exact dates - simple Monday anchors such as `first monday of may` - looser weekly anchors such as `a monday in april` - relative dates if they can be resolved cleanly If the user gives only a month: - for broad inspiration, choose a plausible Monday in that month and state it - for a highly specific weekly opening, ask which Monday if the distinction matters If the campaign year is fictional or far-future: - use the closest real-world Los Angeles week that matches the month and season - prefer signals that are cyclical, seasonal, institutional, or recurring on calendars - treat current headlines only as optional inspiration, not as the default - state that the pressure is borrowed from an equivalent real LA week and then extrapolated forward Weather and season handling: - use broad seasonal logic when exact meteorology is unnecessary - phrases like `early summer heat`, `dry autumn wind`, `marine layer mornings`, `holiday traffic`, or `late-fire-season nerves` are often enough - only get more precise if the user explicitly needs exact weather research ## Workflow ### 1. Resolve the week Turn the date anchor into one absolute Monday or one absolute week window. Prefer Monday-based framing because it is the cleanest input for: - weekly scenario setup - `LAPD Blues` - `roll call` - side-lane generation Also establish: - the season in Los Angeles - the likely city mood for that period - broad weather texture if it affects street life, traffic, crowds, fatigue, or tempers ### 2. Pull recurring Los Angeles signal Browse for LA week activity using primary sources first. Prefer signals that are likely to recur or to have stable equivalents across years. Priority order: 1. official city or public calendars 2. official cultural and venue calendars 3. official sports schedules and team calendars 4. official recurring seasonal and civic calendars 5. transportation, traffic, or civic-disruption sources when relevant 6. high-signal city guides only when primary sources are thin Good source families include: - City of Los Angeles calendars - department calendars when relevant - Discover Los Angeles listings - official team schedules - official venue schedules - Metro, DOT, or road / transit disruption sources when useful Prefer: - opening weekends, annual festivals, parade seasons, fair periods, awards seasons, sports runs, school-year rhythms, tax-season stress, tourism spikes, beach and heat patterns, wildfire season, holiday weekends, civic anniversaries, and convention traffic Be cautious with: - breaking scandals - exceptional crimes - single-year protest waves - celebrity-specific noise that has no stable equivalent later Those can still be useful, but they belong more naturally in a separate institutional or inspiration skill unless the user explicitly asks for them. ### 3. Filter for police relevance Do not return a tourist brochure. Prefer events and pressures that can plausibly generate: - crowd management - traffic stress - vice and nightlife opportunities - violence or disorder risk - protest or political friction - PR pressure - interservice friction - neighborhood overload - public fatigue, heat, weather, pollution, or body constraints If two options are available, prefer the one that tells us something stable about how Los Angeles behaves in that part of the calendar. ### 4. Translate into COPS consequences For each strong event or pressure, answer: - what will civilians do - what will criminals or opportunists do - what will the city or media say - what will other services do - what would this mean for a COPS unit this week This is the most important step. The output should feel like police weather, not like event planning. When extrapolating into 2030+, preserve the pattern, not the exact headline. For example: - keep festival overload, not one named artist unless the user wants color - keep awards-week pressure, not one exact nominee scandal - keep opening-day stadium traffic, not one exact box score For each event retained in the final output, provide: - the event name if it is a real event - one short line explaining what it is about - four police-relevance bullets moving from classic to more indirect or more creative implications Those four bullets should usually follow this gradient: 1. direct uniform / patrol consequence 2. operational or interservice consequence 3. opportunistic crime or public-order consequence 4. indirect, unusual, or highly playable side-pressure ### 5. Separate main-lane fuel from side-lane fuel Unless the user explicitly asks for scenario seeds, treat this skill primarily as a side-lane and ecosystem generator. That means the default output should favor: - connected police work - background noise - side investigations - support scenes - pressure beats for hierarchy, media, dispatch, or other units Not: - a fully invented core scenario If the user wants scandals, police corruption inspiration, institutional crises, or historical analogues, that is adjacent work but not the default output mode of this skill. ### 6. Package the result for reuse Return the signal in a form other skills can consume. Preferred output sections: - `Resolved week` - `Week identity` - `Season and weather texture` - `Recurring city rhythms` - `Major events` - `Medium events` - `Minor events` - `Police consequences` - `Good side lanes` - `Background noise / COPS Channel` - `Cautions` ## Output modes ### Quick week brief Use when the user just wants a fast answer. Return: - resolved date - season and weather texture - 1 to 2 major events - 2 to 3 medium events - 2 to 4 minor events - for each event: what it is, plus four police-relevance bullets from classic to creative ### Scenario inspiration pack Use when the user wants creative help from the city. Return: - resolved week - season and weather texture - strongest real pressures - strongest recurring rhythms - 3 to 5 side-lane ideas - 2 to 3 possible thematic or institutional angles - events grouped into major, medium, and minor tiers - for each event: what it is, plus four police-relevance bullets from classic to creative ### Roll call input pack Use when another skill will write `LAPD Blues` or `roll call`. Return: - resolved week - season and weather texture - city talking points - police pressures - pair-worthy side assignments - one or two hierarchy or interservice complications - major, medium, and minor events ranked by how much they should be felt in the room ## Guardrails - Do not dump too many events. - Do not flatten everything into the same level of importance. - Do not treat every major event as a riot. - Do not make everything gang-related. - Do not invent closures, protests, or incidents unless sourced or clearly marked as inference from the event. - Do not overfit to whatever is loud in today's headlines if the campaign is in 2030 or later. - Do not confuse recurring city life with one-off media panic. - Do not replace the GM's main lane unless explicitly asked for inspiration. - Prefer one strong week identity over ten disconnected facts. - Keep the four consequence bullets varied; they should not all say `crowd control` in different words. ## Combination rule This skill combines especially well with: - `/Users/ludovicfleury/.codex/skills/cops-rollcall-writer/SKILL.md` - future scenario ideation or shaping skills It is especially useful upstream of: - roll call writing - side-lane generation - LA seasonal pressure packs - future institutional inspiration skills for scandals, police politics, or historical analogues Think of this skill as: city signal in, police week pressure out.