Skip to content

iamwaqargulzar/Marketing-Agent-OS / overlays/marketing-os

marketing-os

Verified

Route complex marketing work across strategy, narrative, SEO/GEO, CRO, lifecycle, paid, social, influencer, launch, sales and measurement. Use for broad marketing plans, multi-channel work, or when the right specialist skill is unclear.

FileKindSize
SKILL.mdskill md4.8 KB
references/source-library.mdmarkdown1.8 KB

references/source-library.md

View on GitHub
# Complete source library

Each archive under `assets/` in the installed `marketing-os` folder contains the complete tracked tree of one pinned repository. This includes the original skills, commands, agents, helpers, registries, dashboards, hooks, tests, templates, licenses, and host configuration wherever provided by that source. Relative paths in the original workflows start at their extracted source root.

| Archive | Workflows |
|---|---|
| `source-a.tar.bz2` | Marketing operations, registries, scoring, connectors and dashboards |
| `source-b.tar.bz2` | SEO, analytics, audits, extensions and specialist agents |
| `source-c.tar.bz2` | GEO, AI visibility, reports and specialist agents |
| `source-d.tar.bz2` | Product marketing, growth, copywriting, lifecycle and provider CLIs |

From the installed router folder, list the contents with `python3 -m tarfile -l assets/source-a.tar.bz2`. To use an original workflow, extract its archive into a **new empty directory** outside the host's skill discovery directories. For example:

```sh
python3 -m tarfile -e assets/source-a.tar.bz2 /path/to/new/source-a
```

On Windows, use `py -3` in place of `python3`. Read the source's README and the workflow at the path given by the specialist. Run original commands from the extracted directory using the source's declared dependencies. The original sources may use different host conventions. Installing dependencies, enabling hooks, setting credentials, making paid calls, sending, and writing business data require authorization for the specific action. Extraction alone does none of those things.

The portable agent definitions are also available directly in `references/agents/` in this skill. On hosts without named agents, read the relevant definitions and perform their analyses inline.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall