ワンクリックでManusで任意のスキルを実行

main-dofile

スター2

フォーク0

更新日2026年7月8日 08:14

Create or update a main Stata do-file (main.do) running all other scripts. Use for: setting up main.do; or updating main.do when a new do-file is created or renamed.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

dime-worldbank

dime-worldbank/coding-agent-exercise

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

STEPS:

Identify if a main dofile already exists. It may be called main.do, master.do, or run.do. If does not exists, continue with the steps in the "Create Main Do-File" section. If it does exist, continue with the steps in the "Update Main Do-File" section.

Do not try to run the main.do file as a way of verifying that it is correct. Most intended users of this skill will not have a setup where Stata can be executed through the command line. Instead, verify that the main.do file is correct by checking that it contains all of the other do-files in the project in the correct order.

Create Main Do-File

Copy the template from ./templates/main.do to an appropriate location. This should be the root of where other code files are located. If you do not identify an obvious location, suggest locations to the user and ask them to choose one.
Populate the main do-file with the list of all other scripts in the project. Search documentation for the order the scripts should be run. If no order is specified, see if the naming of the scripts can be used to determine the order. If no order can be determined, ask the user to specify the order.

Update Main Do-File

Each time a do-file is added, deleted or renamed, the main do-file should be updated to reflect the change. If a new do-file is added, it should be added to the main do-file in the appropriate order. If a do-file is deleted, it should be removed from the main do-file. If a do-file is renamed, the old name should be removed and the new name should be added in the appropriate order.

Checks after main.do is created or updated

Make sure the root globals are set correctly in the main do-file. Do not use a root path that depends on the working directory. Instead, use the user's computer root to define the project root.
Make sure that the root global is not re-set in any of the other do-files. The root global should only be set in the main do-file.

This includes using cd to change the working directory or setting a global to the users computer root in any of the other do-files.
If you are removing any root globals from other do-files, make sure to replace those globals with the global that is set in the main do-file such that all do-files are using the same root global.

Use do not run — do echoes commands to the log; run silences them. Prefer do for reproducibility.
Clear state — begin with clear all and set more off to avoid carry-over state.
Version pin — use version to pin Stata version for forward compatibility.

このリポジトリの他の Skills

同じリポジトリ

agent-policy

dime-worldbank/coding-agent-exercise

Human-in-the-loop decision policy for World Bank-style development research coding agents. Use when an agent works on Lumora training data, Stata do-files, survey/payment data, field quality checks, or slide updates and must decide whether to ask the human, use a default, document an assumption, or proceed.

2026-07-062

development-data-caution

dime-worldbank/coding-agent-exercise

Responsible-language and claim-discipline skill for development research and operations. Use when describing vulnerable households, survey staff, payment providers, field quality flags, welfare changes, targeting results, or policy/operational implications from synthetic or real World Bank-style data.

2026-07-062

field-data-quality-hfc

dime-worldbank/coding-agent-exercise

High-frequency field data quality skill for World Bank survey and operations workflows. Use when reviewing Lumora follow-up surveys, survey logs, payment records, back-checks, field visits, enumerator effects, completeness, distribution, consistency, or operational follow-up priorities.

2026-07-062

reproducible-development-data-analysis

dime-worldbank/coding-agent-exercise

Reproducible development microdata analysis skill for Stata. Use when cleaning Lumora household, follow-up, payment, survey log, field visit, or back-check data; building processed datasets; validating IDs and merges; creating Stata tables/figures; or adapting World Bank/DIME-style analysis scripts.

2026-07-062

wb-do-file-reader

dime-worldbank/coding-agent-exercise

World Bank-style Stata do-file and analysis-script reader. Use when inspecting `.do`, Python, or R scripts to understand generated tables, figures, samples, indicator definitions, merge logic, hardcoded numbers, and the provenance of claims before updating a deck or briefing.

2026-07-062

wb-powerpoint-updater

dime-worldbank/coding-agent-exercise

Programmatic PowerPoint update skill for World Bank-style project decks. Use when updating an existing baseline PPTX with new generated Stata figures, tables, output provenance, slide-source mapping, restrained institutional styling, and an update log.

2026-07-062

STEPS:

Identify if a main dofile already exists. It may be called main.do, master.do, or run.do. If does not exists, continue with the steps in the "Create Main Do-File" section. If it does exist, continue with the steps in the "Update Main Do-File" section.

Create Main Do-File

Copy the template from ./templates/main.do to an appropriate location. This should be the root of where other code files are located. If you do not identify an obvious location, suggest locations to the user and ask them to choose one.

Populate the main do-file with the list of all other scripts in the project. Search documentation for the order the scripts should be run. If no order is specified, see if the naming of the scripts can be used to determine the order. If no order can be determined, ask the user to specify the order.

Update Main Do-File

Each time a do-file is added, deleted or renamed, the main do-file should be updated to reflect the change. If a new do-file is added, it should be added to the main do-file in the appropriate order. If a do-file is deleted, it should be removed from the main do-file. If a do-file is renamed, the old name should be removed and the new name should be added in the appropriate order.

Checks after main.do is created or updated

Make sure the root globals are set correctly in the main do-file. Do not use a root path that depends on the working directory. Instead, use the user's computer root to define the project root.

Make sure that the root global is not re-set in any of the other do-files. The root global should only be set in the main do-file.

This includes using cd to change the working directory or setting a global to the users computer root in any of the other do-files.

If you are removing any root globals from other do-files, make sure to replace those globals with the global that is set in the main do-file such that all do-files are using the same root global.

Use do not run — do echoes commands to the log; run silences them. Prefer do for reproducibility.

Clear state — begin with clear all and set more off to avoid carry-over state.

Version pin — use version to pin Stata version for forward compatibility.

name	main-dofile
description	Create or update a main Stata do-file (main.do) running all other scripts. Use for: setting up main.do; or updating main.do when a new do-file is created or renamed.