Schedule Quantity Reconcile logo

Schedule Quantity Reconcile

Organization
AlpacaLabsLLC
schedule-quantity-reconcile

Compare scoped quantity snapshots and explain matches, missing rows and conflicts. Use to reconcile drawing, report or schedule counts; not to extract source documents or update adopted records.

Overview

PublisherAlpacaLabsLLC
Repositoryskills-for-architects
Skill nameschedule-quantity-reconcile
Stars
386
Forks
81
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by AlpacaLabsLLC on GitHub. Read the source before you install it.

Installation

Install the Schedule Quantity Reconcile AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/AlpacaLabsLLC/skills-for-architects/tree/main/skills/schedule-quantity-reconcile
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/AlpacaLabsLLC/skills-for-architects.git /tmp/skills-for-architects
mkdir -p .claude/skills
cp -r /tmp/skills-for-architects/skills/schedule-quantity-reconcile .claude/skills/schedule-quantity-reconcile
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Schedule Quantity Reconcile in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Schedule Quantity Reconcile on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Schedule Quantity Reconcile is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

/as:schedule-quantity-reconcile — Reconcile sourced quantities

Before acting, read the host contract and declaration (skill:schedule-quantity-reconcile), using its profiles from the catalog. No source or write access is implied.

Use the host adapter and available native tools or ordinary task-specific code. Operation names identify semantic procedures, not installed functions. No Arch Studio runner, package installation or executable reconstruction is required. Existing exact authorization persists; ask only for material missing information or permission.

Input: two source-identified quantity snapshots and explicit building/floor/phase/revision scope. Output: a read-only comparison, not an authoritative merged schedule. Project instructions apply when bound to a project; one-off comparison does not initialize or adopt records.

  1. Read both actual inputs and preserve hashes/locators. Drawing extraction belongs to /as:drawing-quantity-extract. Do not compare a whole-campus inventory against one floor as though their denominators match. Missing scope or unit evidence remains unresolved.
  2. Read native evidence procedures. Prepare exact tag/scope/unit keys and preserve every contributing source row. Explicitly resolve aliases or unit conversions using source evidence before comparison; no fuzzy match or automatic phase/room synonym.
  3. Apply schedule_reconcile.compare with native computation under its evidence procedure. Duplicate keys require explicit aggregation or conflict resolution first. Unknown is null, not zero; absent rows are not zero. Matching supplied values proves agreement, not correctness or completeness. Lighting reports first use /as:lighting-report-extract to distinguish inventory from calculation surfaces. Never sum repeated room inventory to remove duplicate keys. Before projecting normalized groups to tag/scope/unit, explicitly select matching source revisions, rooms, scenes and variants on both sides, or preserve those distinctions in the agreed comparison scope. Keep every contributing locator; do not flatten unresolved/conflicting identity into an authoritative quantity. The comparison rejects duplicate comparison keys; it does not choose or merge lighting inventories.
  4. Explain each discrepancy with locators on both sides and source coverage. A revision note can explain a split but does not authorize changing labels or records. Preserve competing values; distinguish a proposed correction from an approved one. Product identity/spec discrepancies route to /as:product-audit; do not enlarge this skill into a general product audit.
  5. Return matched, conflicting, missing and unknown groups. Save only an authorized derived report and read it back; do not change original files. Adopted changes go to /as:master-schedule with explicit selected changes and expected revisions. Missing host capability yields a bounded handoff, not a fabricated match or silent fallback. On retry, reread input hashes before reusing results.

Current document placement

Save only authorized derived outputs and verify their actual content, source hashes and complete requested scope. Inline answers and one-off files need no project setup or adoption. For a requested registered project report, resolve confirmed coordinates using the receive-owned native documents.resolve/register semantics in the workspace model, including its complete document/register mutation sequence. Find existing records with documents.query; never guess a folder. This conditional handoff does not authorize schedule or library changes.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Schedule Quantity Reconcile AI skill do?

Compare scoped quantity snapshots and explain matches, missing rows and conflicts. Use to reconcile drawing, report or schedule counts; not to extract source documents or update adopted records.

Why use Schedule Quantity Reconcile on TypingMind?

Because you install it once and use it with any model. Schedule Quantity Reconcile is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Schedule Quantity Reconcile in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/AlpacaLabsLLC/skills-for-architects/tree/main/skills/schedule-quantity-reconcile. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Schedule Quantity Reconcile?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Schedule Quantity Reconcile?

As many as you like. As long as a model supports skills, you can use Schedule Quantity Reconcile with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Schedule Quantity Reconcile AI skill free?

Yes. It is published on GitHub by AlpacaLabsLLC under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇