Run any Skill in Manus with one click

workflow-artifact-contract

Stars0

Forks0

UpdatedJune 15, 2026 at 06:59

Shared contract for repo-local Codex workflow artifacts. Use when creating, updating, or reviewing custom agents, wrapper skills, and their validation so paths, minimal schemas, and role boundaries stay consistent.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

a129924

a129924/mlops-async

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	workflow-artifact-contract
description	Shared contract for repo-local Codex workflow artifacts. Use when creating, updating, or reviewing custom agents, wrapper skills, and their validation so paths, minimal schemas, and role boundaries stay consistent.

Workflow Artifact Contract

Use this skill when work touches repo-local Codex workflow artifacts under ./.codex/agents/ or ./.agents/skills/.

Contract

Custom agents live only at ./.codex/agents/*.toml.
Reusable skills live only at ./.agents/skills/<skill-name>/SKILL.md.
Per-skill metadata lives only at ./.agents/skills/<skill-name>/agents/openai.yaml.
Do not create workflow artifacts under ./codex/**, ./agents/**, ./.agents/openai.yaml, or ./.codex/openai.yaml.

Custom Agent Rules

Keep each custom agent TOML minimal.
Only use these keys:
- name
- description
- developer_instructions
Match the filename to name.
Do not add optional fields.
Do not create runtime dependencies on legacy .github/agents/*.agent.md files.

Skill Metadata Rules

Explicit-only workflow skills use this exact metadata:

policy:
  allow_implicit_invocation: false

Do not add interface metadata or repo-specific keys unless a runtime failure explicitly requires them.

Boundary Notes

Legacy .github/agents/*.agent.md files are frozen provenance inputs only.
Wrapper skills describe how a parent Codex session should use custom agents; they are not runtime orchestration engines.
Shared contract skills define reusable rules and validation targets; they should not own topic-specific phase execution.

More from this repository

same repository

python-implementation-workflow

a129924/mlops-async

Wrapper workflow recipe for parent Codex sessions that need to coordinate Python topic delivery with repo-local planner, implementer, and reviewer agents while preserving shared artifact-contract boundaries.

2026-06-150

api-client-porting-implementer

a129924/mlops-async

Implement one source SDK API or safe same-family batch from planner output using request-test-first porting, minimal implementation, response and error contract checks, optional tracker updates, and an explicit final decision.

2026-06-150

api-client-porting-planner

a129924/mlops-async

Plan a source SDK API client port before implementation by collecting source evidence, drafting request contracts, classifying risk and stop flags, and preparing implementer handoff output for one endpoint family or safe same-family batch.

2026-06-150

plan-step-tracker

a129924/mlops-async

Query step status (pending/done) in plan/<topic>/<topic>.step.md with minimal token cost and explicit blocking when incomplete.

2026-06-150

sense-env-scaffold

a129924/mlops-async

Run the sense_env.py scaffold to discover or assert facts about the repository environment. Use this when you need a structured JSON snapshot of the current environment state, or when you need to evaluate a contract's sensing assertions.

2026-06-150

python-naming

a129924/mlops-async

Define or normalize Python naming conventions for identifiers, files, folders, and visibility boundaries. Use this when drafting or reviewing Python code style rules centered on names.

2026-06-120

name	workflow-artifact-contract
description	Shared contract for repo-local Codex workflow artifacts. Use when creating, updating, or reviewing custom agents, wrapper skills, and their validation so paths, minimal schemas, and role boundaries stay consistent.

Workflow Artifact Contract

Use this skill when work touches repo-local Codex workflow artifacts under ./.codex/agents/ or ./.agents/skills/.

Contract

Custom agents live only at ./.codex/agents/*.toml.
Reusable skills live only at ./.agents/skills/<skill-name>/SKILL.md.
Per-skill metadata lives only at ./.agents/skills/<skill-name>/agents/openai.yaml.
Do not create workflow artifacts under ./codex/**, ./agents/**, ./.agents/openai.yaml, or ./.codex/openai.yaml.

Custom Agent Rules

Keep each custom agent TOML minimal.
Only use these keys:
- name
- description
- developer_instructions
Match the filename to name.
Do not add optional fields.
Do not create runtime dependencies on legacy .github/agents/*.agent.md files.

Skill Metadata Rules

Explicit-only workflow skills use this exact metadata:

policy:
  allow_implicit_invocation: false

Do not add interface metadata or repo-specific keys unless a runtime failure explicitly requires them.

Boundary Notes

Legacy .github/agents/*.agent.md files are frozen provenance inputs only.
Wrapper skills describe how a parent Codex session should use custom agents; they are not runtime orchestration engines.
Shared contract skills define reusable rules and validation targets; they should not own topic-specific phase execution.