majesticway-task-creation

Generate standardized AEC benchmark task instances from MajesticWay residential project data.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/robikscube/SJ-skills-sandbox --skill majesticway-task-creation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: majesticway-task-creation
Source: https://github.com/robikscube/SJ-skills-sandbox/tree/main/Skill-List/majesticway-task-creation
Command: npx skills add https://github.com/robikscube/SJ-skills-sandbox --skill majesticway-task-creation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the time-consuming and error-prone process of manually formatting AEC benchmark tasks to meet Harbor conventions, ensuring consistency and evaluability for AI agent testing on real construction project documents.

Core Features & Use Cases

It provides end-to-end guidance for designing task instances across all scopes (intrasheet, intradrawing, intraproject) and task families, including defect injection for error detection tasks, navigation task design, verifier script authoring, and local validation. For example, AEC AI researchers can use this skill to quickly generate a new test instance that checks if an agent can detect a mismatched wall cavity dimension between a construction drawing and employer's requirements document.

Quick Start

Use this skill to create a new defect-detection task for the MajesticWay ground floor plan by selecting a source PDF, defining an injected dimension error, and generating the required task.toml, instruction.md, and test.sh files following the provided Harbor format guidelines.

Frequently Asked Questions about majesticway-task-creation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate AEC benchmark tasks for evaluating AI agents on construction documents?

You can generate AEC benchmark tasks by creating standardized instances from MajesticWay project data, covering scopes like intrasheet and intraproject, to evaluate information-retrieval and multimodal AI agents on construction documents.

What is the process for injecting synthetic defects into construction drawings for AI evaluation?

Synthetic defect injection involves defining errors like mismatched dimensions within source PDFs and generating the required task.toml, instruction.md, and test.sh files to test if AI agents can detect the injected construction document defects.

How do I format construction document QA tasks to meet Harbor benchmark requirements?

Formatting construction document QA tasks for Harbor benchmarks requires setting up the correct file structure and authoring verifier scripts, followed by local task validation to ensure consistency and evaluability for AI agent testing.

Can I use this approach to test cross-reference resolution between specs and drawings?

Yes, you can design task instances for cross-reference resolution and spec-drawing synchronization, allowing you to test whether an AI agent can detect mismatches between employer requirements and construction drawings.

What file formats and structures are needed to validate local AI agent tasks against benchmark conventions?

Local validation against benchmark conventions requires generating specific files including task.toml, instruction.md, and test.sh, while ensuring the overall file structure properly supports the defined task scopes and injected construction defects.

Why do I need a standardized format for multimodal AI agent evaluation in construction workflows?

A standardized format eliminates the time-consuming manual formatting process, ensuring consistency and evaluability across different test instances when evaluating multimodal AI agents on real construction project documents.