agentsclimarketplace

Master schedule

Skill AlpacaLabsLLC/skills-for-architects/skills/master-schedule

Initialize, validate, inspect, or import the current project's local FF&E product library. Use when a product workflow needs product-library.csv, when the user invokes /as:master-schedule, or when legacy master-schedule.json or canoa.json configuration is present.From its SKILL.md

Install
npx -y skills add AlpacaLabsLLC/skills-for-architects --skill master-schedule

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

4.6 KB, as published. Nobody here has run it

/as:master-schedule — Local product library

<!-- architecture-studio:harness-compatibility -->

Harness note: use /as:<skill> on Claude Code and $<skill> on Codex. Resolve <skill-root> as the directory containing this loaded SKILL.md and <plugin-root> as the plugin root that contains skills/, and use equivalent native tools when host tool names differ.

Manage the current project's product-library.csv. This workflow is local-only: do not use a network service, connector, account, spreadsheet identifier, or MCP tool.

Use the deterministic helper instead of constructing or changing CSV with ad hoc shell or prompt logic:

python3 "<plugin-root>/skills/master-schedule/scripts/csv-library.py" status product

The helper resolves the nearest project root by walking upward to PROJECT.md. The canonical schema is <plugin-root>/schema/product-schema.md; storage rules are in <plugin-root>/schema/csv-conventions.md.

Automatic use by product skills

  1. Run status product from the user's current working directory.
  2. If the valid library exists, continue silently.
  3. If it is missing and no legacy configuration exists, preview creation at the resolved project root. Use the single interaction gate once, then run init product after confirmation.
  4. If the library is invalid, stop. Explain the header or row error and leave the file unchanged.
  5. Never initialize outside a directory governed by PROJECT.md.

Manual use

When the user invokes /as:master-schedule directly:

  • Existing valid library: report its path and data-row count from status product.
  • Missing library: preview the exact path, explain that initialization creates only the 33-column header, use one confirmation gate, then run init product.
  • Invalid library: report the validation failure without writing.
  • Empty existing file: it may be initialized after the same preview and confirmation.

Do not ask in prose whether to proceed immediately before presenting an approval gate. The gate itself is the question.

User-exported CSV import

Import is explicit and never automatic:

python3 "<plugin-root>/skills/master-schedule/scripts/csv-library.py" import product --source "/absolute/path/to/user-exported.csv"

Before import, state the source and target paths and that the complete source will be validated against the exact 33-column schema. Use one confirmation gate. The helper refuses a malformed source and refuses to overwrite a populated target.

For a reviewed operation that intentionally replaces the complete populated library, use the explicit replacement flag after preview and confirmation:

python3 "<plugin-root>/skills/master-schedule/scripts/csv-library.py" import product --source "/absolute/path/to/reviewed-library.csv" --replace-existing

This validates the complete candidate and current library before one guarded atomic replacement. It fails closed if either file is malformed or if the target changes after validation. Never add this flag to ordinary setup or import.

Legacy evidence

master-schedule.json and canoa.json may point to a library used by an earlier release. They contain configuration, not recoverable rows.

  • Preserve both files byte-for-byte.
  • Do not rename, delete, rewrite, or contact anything named inside them.
  • Explain that connectivity was removed in Architecture Studio 1.4.
  • Ask the user to export the former library as CSV, then use the explicit user-exported CSV import flow.

Mutation boundary for other skills

Use the same helper for safe operations:

# Validate the complete file
python3 "<plugin-root>/skills/master-schedule/scripts/csv-library.py" validate product

# Append values supplied as a JSON object keyed by schema column
python3 "<plugin-root>/skills/master-schedule/scripts/csv-library.py" append product --row-json "/path/to/row.json"

# Update exactly one matched row with a partial JSON object
python3 "<plugin-root>/skills/master-schedule/scripts/csv-library.py" update product --match-column "SKU" --match-value "ABC-123" --row-json "/path/to/changes.json"

All mutations validate the complete existing file before writing and atomically replace it from a temporary file in the same directory. A failed validation or mutation must leave the source unchanged.

What ships with it: 2 files

11.1 KB alongside SKILL.md, 1 of them executable

scripts/

Gives 0 of the 12 instructions most project setup skills give

Counted across 1,553 of the 3,091 authors here whose files we hold, read 2026-09-06

  • Write the configuration filein 36 of 1553
  • Create the directory structurein 35 of 1553, across 33 files
  • Verify the setupin 31 of 1553, across 28 files
  • Run the setup scriptin 30 of 1553, across 29 files
  • Pre-determine the required sample sizein 29 of 1553, across 12 files
  • Check if the configuration already existsin 29 of 1553
  • Document every testin 26 of 1553, across 10 files
  • Start with a hypothesisin 26 of 1553, across 11 files
  • Ask one question at a timein 22 of 1553
  • Test a single variable per testin 21 of 1553, across 9 files
  • Read product marketing context before asking questionsin 19 of 1553, across 8 files
  • Do not peek and stop earlyin 18 of 1553, across 7 files

Said here and by no other author read

  • Run status product from working directory
  • Preview creation before initializing library
  • Stop if library is invalid
  • Validate complete file before mutation
  • Preserve legacy configuration files byte for byte

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 613,297. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.