Showing 12061–12090 of 15675 skills
Prepare and run bounded SUMO/TraCI traffic scenarios, inspect a Simulation Canvas and query reproducible road or multimodal evacuation experiments.
Ran2424/transportx-agent
Studies everything that has to reach a site and finds where two of them want the same frontage: lists every arrival — people, cars, deliveries, refuse, fire apparatus, utilities, moving vans, coaches — traces each from the public way to where it has to end up, and reports the conflicts, the curb cuts that will not be granted, and the frontage the project has already spent. Trigger on "site access study", "how does the truck get in", "where does the fire access go", "can we get a curb cut here", "loading and refuse access", "site-access-study", or a site plan with a question about how anything reaches it. Carries no dimensions, no turning radii, no fire apparatus requirements and no curb cut standards; all come from the jurisdiction, the fire department and the utility. It does no traffic engineering and no swept path analysis, and does not replace the civil engineer or the Architect of Record.
DavidCho1999/archaiflow-skills
Reads any document with money in it — an estimate, a budget, a cost plan, a supplier quote, a contractor's proposal, a client's own number — and does the part an architect can do without being an estimator: establish what it covers, what it excludes, what it assumed, and what date it is on. Those four decide almost every argument about a price, and none of them require checking the arithmetic. Trigger on "read this estimate", "what does this quote actually include", "the budget came back", "is this number comparable", "cost-reader", or any priced document handed over. Carries no rates, no benchmarks and no cost data; `/lookup-cost` quotes a benchmark with its source and `senior-cost-estimator` gives judgement. It checks no arithmetic, prices nothing, and does not replace the estimator, the contractor, or the Architect of Record.
DavidCho1999/archaiflow-skills
Sorts a delay before it becomes a claim: establishes what is actually late against what baseline, whether the delayed activity was ever controlling the completion date, who caused it, and whether the contract makes it compensable, excusable, or neither. Separates the three questions that get merged — is it late, is it critical, and whose is it — because a delay can be real and cost nobody anything. Trigger on "we are behind", "the contractor says we delayed them", "is this a critical delay", "do we owe them time", "delay-triage", or a delay asserted with a letter likely to follow. Carries no contract terms and no float conventions; entitlement comes from the executed agreement you quote. It is not a delay analysis, which is forensic and has a methodology, and it does not replace the scheduler, the attorney, or the Architect of Record.
DavidCho1999/archaiflow-skills
Reads any photograph an architect ends up with — a site visit, an existing building, a defect somebody wants explained, a phone picture from a client, a product on a shelf — and separates what is visible from what is inferred, because a photograph is the most persuasive and least complete document on a project. Establishes when and where it was taken and which way the camera faced before reading anything, since a photograph with no location is evidence of nothing. Trigger on "read this photo", "what am I looking at here", "the client sent a picture", "is this a problem", "photo-reader", or an image handed over with a question. Carries no dimensions and measures nothing from an image. It diagnoses nothing: a photograph of a stain is not a diagnosis, and `leak-triage` takes it from there. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Investigates whether analytical data is ready by separating configured schedules and freshness expectations from locally observed timestamps and run artifacts. Use when data appears stale, late, incomplete, or unavailable, and before raising a freshness threshold or silencing a failing check; it explains timing evidence and gaps without inventing runtime history or querying external systems.
analyticsengineering/ae-toolkit
Defines canonical business metric contracts with explicit population, grain, formula, dimensions, time semantics, ownership, and acceptance cases. Use when a KPI needs an authoritative definition, competing definitions must be reconciled, or a metric contract must be specified before implementation.
analyticsengineering/ae-toolkit
Coordinates name-only renames of analytical models, columns, relations, sources, metrics, semantic objects, and every repository reference while preserving the data contract. Use for atomic internal column renames and cross-layer reference updates; use migration-plan when behavior/schema changes or a published consumer interface needs compatibility and phased cutover.
analyticsengineering/ae-toolkit
Traces a column, metric, or business figure through models and BI artifacts to its source, and explains what it actually measures. Use when asked where a number comes from, what a metric means, what depends on a field, or why two reports disagree.
analyticsengineering/ae-toolkit
Investigates whether analytical data is ready by separating configured schedules and freshness expectations from locally observed timestamps and run artifacts. Use when data appears stale, late, incomplete, or unavailable, and before raising a freshness threshold or silencing a failing check; it explains timing evidence and gaps without inventing runtime history or querying external systems.
analyticsengineering/ae-toolkit
Defines canonical business metric contracts with explicit population, grain, formula, dimensions, time semantics, ownership, and acceptance cases. Use when a KPI needs an authoritative definition, competing definitions must be reconciled, or a metric contract must be specified before implementation.
analyticsengineering/ae-toolkit
Coordinates name-only renames of analytical models, columns, relations, sources, metrics, semantic objects, and every repository reference while preserving the data contract. Use for atomic internal column renames and cross-layer reference updates; use migration-plan when behavior/schema changes or a published consumer interface needs compatibility and phased cutover.
analyticsengineering/ae-toolkit
Traces a column, metric, or business figure through models and BI artifacts to its source, and explains what it actually measures. Use when asked where a number comes from, what a metric means, what depends on a field, or why two reports disagree.
analyticsengineering/ae-toolkit
Run the real {{APP_NAME}} the way users reach it, drive it, and capture evidence (screenshot, console errors, performance trace, heap snapshot). Use to reproduce a bug report, verify a fix or feature before claiming it works, or measure performance. Never report "should work" without evidence from a real run.
epistex-dev/poteto-kit
Tatsh/re3-installer
Powerful asynchronous state management, server-state utilities, and data fetching for TS/JS, React, Vue, Solid, Svelte & Angular.
benschac/snap_post
stribus/pygerengastos
a5c-ai/babysitter
Analyze geospatial data using geopandas with proper coordinate projections. Use when calculating distances between geographic features, performing spatial filtering, or working with plate boundaries and earthquake data.
DANG-ai/SKILLER
A good starting point for GLM calibration tasks. Use to inspect glm3.nml, confirm how GLM runs, and identify the relevant files before moving on to calibration and output evaluation.
DANG-ai/SKILLER
Output-processing guidance for GLM tasks. Especially useful after glm-basics and glm-calibration when you need verifier-matching metrics from output.nc and a final /root/metrics.json.
DANG-ai/SKILLER
Plans and tracks tasks in .claude/harness/plans.json. Use when creating plans, adding tasks, updating markers, checking progress, or brainstorming an idea into tasks.
tim-hub/powerball-harness
Executes plans.json tasks — solo, parallel, or breezing team mode. Use when implementing tasks or running the work loop.
tim-hub/powerball-harness
Periodic housekeeping and session lifecycle management. Use when performing cleanup, pruning, or session commands.
tim-hub/powerball-harness
Triggers once per project, when migrating an existing in-flight project into the backlog-file model — e.g. "/project-onboard" — and (1) detects and resolves PRD/decisions/progress conflicts, (2) consolidates the accumulated single decisions and progress files into the new format **one file each** (decisions = table form, progress = completed items only), (3) tidies the folder structure and LOREMASTER.md, after which the project switches to per-backlog-item files (detection by AI, judgment by humans).
loremaster-ai/loremaster
Turn each photo into a 3:4 postcard with a faithful photograph above and a warm, quirky crayon recollection below. Use when visible wax grain and personal travel journal charm are desired; do not use for acrylic, watercolor, or polished cartoons.
AlbertAZ1992/image-skillbook
Turn a supplied person, landmark, or landscape photo into a strict 3:4 editorial poster: a small premium enamel keepsake above and the authentic source photograph below. Use for collectible travel-memory posters, not standalone product renders.
AlbertAZ1992/image-skillbook
Turn each photograph into a 3:4 editorial diptych with the faithful photo above and a tactile oil-paint miniature world below. Use for sculptural palette-knife relief and diorama-like scenes; do not use for flat digital art or plastic 3D renders.
AlbertAZ1992/image-skillbook
Re-read a supplied photo as a 3:4 editorial story where its real photographic subject interacts with a few tiny black-line doodle figures. Use for warm, playful human or pet narratives; do not use when the source subject should become a full illustration.
AlbertAZ1992/image-skillbook
fabioc-aloha/Alex_Skill_Mall