AGENT SKILL

coderos-marketos-dev

暂无简介

License 许可
MIT
最近更新
2026-10-07
Stars
★ 1
Forks
0

03 SKILL.md 正文

Skill: CoderOS MarketOS Development

Use this skill when an agent is asked to use CoderOS to plan, scope, route, validate, or implement work for MarketOS.

This skill is for CoderOS-side project activation. It must not make MarketOS depend on CoderOS at runtime.

1. Use this skill when

Use this skill for:

  • creating a MarketOS development objective
  • classifying a MarketOS task
  • selecting a MarketOS work-order template
  • mining OSS targets before implementation
  • assigning an AI lane
  • preparing a MarketOS PR prompt
  • auditing MarketOS PR evidence
  • transferring CoderOS patterns into MarketOS-native code
  • validating that CoderOS remains a development control plane only

2. Do not use this skill for

Do not use this skill to:

  • modify CoderOS runtime files
  • modify MarketOS directly from this repository
  • store credentials
  • activate providers
  • run ads
  • place supplier orders
  • mutate external browser surfaces
  • create GitHub issues automatically
  • auto-merge PRs
  • treat profile JSON as live MarketOS runtime config

3. Required read order

Read these files before creating a MarketOS prompt or work order:

  1. projects/marketos/project_profile.json
  2. projects/marketos/domain_roles.json
  3. projects/marketos/verification_commands.json
  4. projects/marketos/cost_policy.json
  5. projects/marketos/context_policy.json
  6. projects/marketos/source_leverage_targets.json
  7. projects/marketos/security_policy.json
  8. the selected template in projects/marketos/work_order_templates/
  9. docs/MARKETOS_DEV_WITH_CODEROS.md
  10. docs/MARKETOS_OPERATOR_COMMAND_SHEET.md

4. Boundary rule

Always preserve this sentence in substance:

CoderOS is the AI development company/control plane used to improve MarketOS; CoderOS is not an operational dependency of MarketOS.

A MarketOS PR should not add imports from CoderOS runtime modules, require CoderOS CLIs for startup, or use CoderOS profile files as production runtime configuration.

5. Task classification

Classify every request by:

Project:
Repository:
Domain:
Role owner:
Template:
Risk tier:
Context tier:
Cost tier:
AI lane:
Allowed files:
Forbidden files:
Source leverage targets:
Validation commands:
Stop conditions:

If these cannot be determined, ask for clarification or produce a planning-only task card rather than implementation instructions.

6. Domain selection

Choose the domain from the request:

  • provider cost governance
  • client workspace isolation
  • resource execution governance
  • public signal pipeline
  • browser scouting sidecar
  • commerce workflow lifecycle
  • TrustOps and security review
  • source leverage and capability mining

Then select the matching role in domain_roles.json.

7. Template selection

Use one of the five templates:

Template Use
provider_cost_governor model/API/provider/ad spend and budget gates
client_workspace_isolation tenant, client, workspace, and TrustOps boundaries
resource_execution_governor dry-run/live approval decisions and resource actions
public_signal_pipeline public signals, scoring, deduplication, opportunity evidence
browser_scouting_sidecar read-only public page and supplier/tool scouting

If none fit, produce a planning gap note and do not invent a sixth template unless explicitly asked.

8. Source leverage requirement

Infrastructure tasks must mine OSS targets first.

Return for each relevant target:

Target:
Reuse mode:
Why useful:
Why safe or unsafe:
Implementation implication:
Decision:

Default reuse mode is copy_pattern or reference_only. Direct dependency adoption requires explicit review.

9. Lane assignment

Assign one lane, not many.

  • Antigravity: large docs, workflows, control-plane and architecture consolidation.
  • Claude: source-mining, integration maps, careful bridges.
  • Jules: bounded safety/recovery work.
  • Grok: policy, cost, gatekeeper, security-audit logic.
  • Hermes: medium implementation only when setup is stable.
  • Orca: read-only cockpit proof until promoted.
  • PowerShell/CoderOS: validation/setup only.

The assigned lane fixes its own lint, tests, conflicts, and wrong-base issues in the same branch.

10. Verification rules

For CoderOS activation-pack changes, use:

python -m compileall repo_dev_runtime tests
python -m ruff check repo_dev_runtime tests
python -m repo_dev_runtime.plan_lifecycle_cli validate --plan docs/plans/active/plan-marketos-coderos-project-profile-v1.md
powershell -File scripts/verify.ps1
git diff --check

For MarketOS implementation PRs, use MarketOS-native focused checks from the relevant repository.

Unrun checks must be declared.

11. Security rules

Stop if the work requires:

  • credentials
  • real client data
  • live provider calls
  • ad spend
  • external order placement
  • write-capable browser automation without approval
  • weakening client isolation
  • making CoderOS a MarketOS runtime dependency

12. Evidence format

Every output must end with:

Lane:
Task:
Project: MarketOS
Domain:
Template:
Branch:
PR:
Changed files:
Additions/deletions:
Source leverage consulted:
Verification commands:
Security posture:
Known risks:
Merge action:
Next dependency:

Keep the evidence concise.

13. Stop conditions

Stop and ask for clarification when:

  • no domain fits
  • no file scope exists
  • a live provider or browser write is requested without approval
  • credentials are required
  • task duplicates an active PR
  • branch base is unclear
  • validation cannot be defined
  • source-leverage review is required but omitted

Do not stop for normal lint/test failures inside the assigned branch. Fix those in the same branch.

04 同仓库更多 Skills