agentsclimarketplace
Sign in

Manage projects

Skill celeryhq/simplified-ai/skills/manage-projects

Organize marketing work in Simplified projects and project items. Use when the user asks to create or inspect a marketing project, campaign workspace, content production board, launch checklist, editorial pipeline, or deliverable list; add, retrieve, prioritize, reorder, assign, export, or remove project items; or turn an approved content plan into trackable work.From its SKILL.md

Install
npx -y skills add celeryhq/simplified-ai --skill manage-projects

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.5 KB, 627 tokens by cl100k_base, as published. Nobody here has run it

Manage Projects

Translate a marketing plan into accountable, sequenced work without confusing project organization with publishing authorization.

Guardrails

  • Inspect before mutating. Reuse an existing project when it clearly matches the user's initiative.
  • Use the same resourcetype for every operation on a project. Prefer Project for ordinary marketing work and AdCreativeProject only for specialized ad-creative projects.
  • Do not invent project, item, partner, or agent IDs. Resolve them from tool results or user-provided values.
  • Creating a project or item does not authorize assigning an agent, exporting content, publishing content, or deleting records.
  • Confirm the target and consequences before soft-deleting a project/item, assigning an execution agent, or exporting to a partner integration.
  • Dates must be realistic and internally ordered. Surface impossible dependencies or missing owners rather than silently compressing the plan.

Workflow

  1. Define the initiative: outcome, scope, deadline, deliverables, channels, approval points, owners, dependencies, and definition of done.
  2. Call api_listProjects with the chosen resourcetype and search term. Reuse a unique match or show choices when several projects could apply.
  3. If creation is requested, call api_createProject with a clear title, concise outcome-based description, and only supported structured data. Preserve the returned project ID.
  4. Call api_listProjectItems before adding work to understand existing deliverables and avoid duplicates.
  5. Convert the plan into outcome-oriented items. Each item should have one deliverable, owner or owner-needed flag, status, priority, start/due date, dependencies in the description or data, and a measurable definition of done.
  6. Call api_createProjectItem for authorized items. Use data.assets for known permanent asset UUIDs; never store signed URLs as durable references.
  7. Use api_reorderProjectItem only when the user requests or approves a new sequence. Use api_assignAgentToItem only with a resolved agent ID and explicit execution scope.
  8. Use api_exportProjectItems only after confirming the partner integration and exact item IDs. Report export initiation separately from export completion.

Read references/project-operations.md for field and lifecycle rules.

Marketing Operations Standard

  • Organize work around deliverables and approvals, not vague activity such as “work on social.”
  • Separate strategy, copy, creative, channel adaptation, compliance, review, scheduling, and reporting when different owners or gates apply.
  • Put the decision deadline before the publish deadline. Include contingency time for legal, customer, or executive review where relevant.
  • Use priorities to express business consequence and sequencing, not urgency theater.
  • Do not create a bloated project for a one-step request; perform the direct task unless the user wants tracking.

Output

Lead with project status and the critical path. Then report created or changed items, owners, dates, dependencies, approval gates, IDs needed for follow-up, and any action awaiting confirmation.

What ships with it: 2 files

2.3 KB alongside SKILL.md

agents/

references/

Gives 0 of the 12 instructions most product growth skills give in 627 tokens

Counted across 694 of the 879 authors here whose files we hold, read 2026-09-06

  • Check for product marketing context firstin 49 of 694, across 20 files
  • Validate the why before building featuresin 18 of 694, across 4 files
  • Respond to every comment in real-timein 17 of 694, across 6 files
  • Structure launch marketing across three channel typesin 16 of 694, across 4 files
  • Recruit early users one-on-onein 13 of 694, across 2 files
  • Ask one question at a timein 13 of 694
  • Rank features using ICE scoringin 12 of 694, across 3 files
  • Identify primary conversion goalin 11 of 694, across 3 files
  • Identify traffic contextin 11 of 694, across 3 files
  • Evaluate headline effectivenessin 11 of 694, across 3 files
  • Check visual hierarchy and scannabilityin 11 of 694, across 3 files
  • Run product diagnosticsin 11 of 694, across 3 files

Said here and by no other author read

  • Inspect before mutating
  • Reuse an existing project when it matches
  • Use the same resourcetype for every operation
  • Resolve IDs from tool results or user values
  • Confirm the target and consequences before deleting
  • Define the initiative clearly

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.