meta-grey-ops SKILL.md skillA
meta-grey-ops from sergeyizmailov/knowledge-delta-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sergeyizmailov/knowledge-delta-skills/meta-grey-ops@git:20261014.8613433Pins git:20261014.8613433 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sergeyizmailov/knowledge-delta-skills
- Path
skills/meta/meta-grey-ops/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261014.8613433, committed Oct 14, 2026
- First version recorded
- Sep 29, 2026
- Size
- 12,648 bytes
- Repository stars
- 3
- License
- MIT
Launches, monitors and operates Meta (Facebook/Instagram) ads for any vertical and offer through the metaops CLI (workspace.json + JSON specs): doctor, plan, apply --confirm SPEND (creates ACTIVE, spends), verify, review/monitor, insights/stats pulls, pause, comment hiding, BM invites, pixels/CAPI, and tokens (System User, or DevTools EAAB/EAAG/EAAd/EAAH/EAAI with cookies + proxy). Grey-market survival: antidetect/proxy hygiene, rejects and disabled accounts, review layer and cloaking…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Meta Grey Ops Launch and operate via API on your own tokens (= autolaunch SaaS without the UI, `13`) + grey survival. Sibling skills (same `meta/` folder): "buy well" → `../meta-ads` · "count & sync" → `../tracker-ops` · "portfolio, kill and scale decisions" → `../senior-buyer-ops` · "is this difference real" → `../measurement-experimentation-ops`. In references, `meta-ads/14`, `tracker-ops/03`, `senior-buyer-ops/01` etc. mean `<skill>/references/NN-*.md` (link `../../<skill>/references/NN-*.md` from a references file, `../<skill>/references/NN-*.md` from this file); bare numbers (`02`, `16`) are this skill's `references/NN-*.md`. ## Start here | You are… | Read | Then | |---|---|---| | In a directory with `workspace.json` | `references/16-metaops-agent-cli.md` | `metaops --workspace … --json` (or the project's wrapper); before `apply --confirm SPEND` read `00` §6–7.5 | | Handed a token / asked to launch anything via API | `references/00-launch-runbook.md` | a workspace in a project dir outside the skill (`scripts/specs/example-workspace.json`), validate, then `metaops` | …
Read the whole file at its exact version.
How to install
mdr add sergeyizmailov/knowledge-delta-skills/meta-grey-ops@sha256:2af29400263d2f74The line at the top of this page pins the label git:20261014.8613433, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_qmvqh2wiyz4zptz6)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 29, 2026 and Oct 14, 2026, about one every 15 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.8613433 latest | 2026-10-14 | 8613433 | 12,648 B | A | view · diff |
| git:20260929.c1f17bd | 2026-09-29 | c1f17bd | 20,723 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (12648 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
sergeyizmailov/knowledge-delta-skills · 3 stars · license MIT · pushed 2026-10-14 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_qmvqh2wiyz4zptz6 GET https://markdownregistry.com/api/v1/resolve?ref=sergeyizmailov/knowledge-delta-skills/meta-grey-ops GET https://markdownregistry.com/api/v1/blob/2af29400263d2f740f9fbfba600b20ed772b42285c3221561334158bcdafe924
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from sergeyizmailov/knowledge-delta-skills
Every file in sergeyizmailov/knowledge-delta-skills