ToolJet Marketplace Plugin Builder
ToolJet/ToolJet
Turns an API description, such as an OpenAPI file or a Postman collection, into a connector plugin for ToolJet's marketplace and checks it with the repo's validator.
Platform specs and publish validation — per-platform requirements and the validate-before-publish step for multi-platform fan-out.
Install Platform Specs And Validation
$ npx skills add social-media-skills/skills --skill platform-specs-and-validation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install social-media-skills/skills platform-specs-and-validation --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/social-media-skills/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/platform-specs-and-validation .claude/skills/platform-specs-and-validation && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "platform-specs-and-validation" agent skill from https://github.com/social-media-skills/skills/tree/main/skills/platform-specs-and-validation into .claude/skills/platform-specs-and-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-specs-and-validation", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/social-media-skills/skills/tree/main/skills/platform-specs-and-validationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add social-media-skills/skills --skill platform-specs-and-validation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install social-media-skills/skills platform-specs-and-validation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/social-media-skills/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/platform-specs-and-validation .agents/skills/platform-specs-and-validation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "platform-specs-and-validation" agent skill from https://github.com/social-media-skills/skills/tree/main/skills/platform-specs-and-validation into .agents/skills/platform-specs-and-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-specs-and-validation", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add social-media-skills/skills --skill platform-specs-and-validation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install social-media-skills/skills platform-specs-and-validation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/social-media-skills/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/platform-specs-and-validation .cursor/skills/platform-specs-and-validation && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "platform-specs-and-validation" agent skill from https://github.com/social-media-skills/skills/tree/main/skills/platform-specs-and-validation into .cursor/skills/platform-specs-and-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-specs-and-validation", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/social-media-skills/skills.git --path skills/platform-specs-and-validation--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add social-media-skills/skills --skill platform-specs-and-validation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install social-media-skills/skills platform-specs-and-validation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/social-media-skills/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/platform-specs-and-validation .gemini/skills/platform-specs-and-validation && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "platform-specs-and-validation" agent skill from https://github.com/social-media-skills/skills/tree/main/skills/platform-specs-and-validation into .gemini/skills/platform-specs-and-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-specs-and-validation", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install social-media-skills/skills platform-specs-and-validationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add social-media-skills/skills --skill platform-specs-and-validation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/social-media-skills/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/platform-specs-and-validation .github/skills/platform-specs-and-validation && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "platform-specs-and-validation" agent skill from https://github.com/social-media-skills/skills/tree/main/skills/platform-specs-and-validation into .github/skills/platform-specs-and-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-specs-and-validation", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add social-media-skills/skills --skill platform-specs-and-validation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install social-media-skills/skills platform-specs-and-validation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/social-media-skills/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/platform-specs-and-validation .opencode/skills/platform-specs-and-validation && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "platform-specs-and-validation" agent skill from https://github.com/social-media-skills/skills/tree/main/skills/platform-specs-and-validation into .opencode/skills/platform-specs-and-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-specs-and-validation", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
platform-specs-and-validation- GitHub stars
- 134
- Token cost
- ~1.6k tokens
- SKILL.md length
- 609 words
- Files
- 6 (incl. references)
- Skills in repo
- 106
- Repo updated
- First seen
- Licence
- MIT
At a glance
Platform specs and publish validation — per-platform requirements and the validate-before-publish step for multi-platform fan-out.
- Fanning a post out to multiple platforms
- SKILL.md covers The POV: publish-ready,…, The framework: CHECK, The spec (ground truth —… and Honest scope (never violate), plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- A post is getting rejected
What it does
Platform Specs And Validation is an agent skill from social-media-skills/skills. Platform specs and publish validation — per-platform requirements and the validate-before-publish step for multi-platform fan-out. Use when fanning a post out to multiple platforms, when a post is getting rejected, when mapping per-platform postType/required fields, or to run the validate-before-publish step. Encodes the per-platform postType enums, required-field matrices, and media rules from the OpenAPI spec, and runs POST /posts/validate so a post lands correctly on every target. Uses the CHECK framework. The…
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `evals/evals.json`, `references/scope-and-connections.md` and `references/the-check-framework.md`).
It sits in Backend & APIs, covering OpenAPI specifications. It works with OpenAPI, Pinterest and TikTok. The repository describes itself as: 106 social media skills for AI agents - strategy, writing, video, design, platform growth, publishing, and analytics. Works with Claude, Cursor, OpenClaw, Hermes & 40+ agents. The licence is MIT.
When your agent uses it
- Fanning a post out to multiple platforms
- A post is getting rejected
- Mapping per-platform postType/required fields
- Run the validate-before-publish step
Example prompts
- “/platform-specs-and-validation”
What it can do on your machine
Read from SKILL.md and the folder at commit 6e30eeb. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Platform Specs And Validation loads about 1.6k tokens when it runs, and up to ~4.6k if it reads all its reference files. Until then it costs about 235 tokens; SKILL.md has 609 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from social-media-skills/skills at commit 6e30eeb, republished under its MIT licence (© social-media-skills). 609 words, ~1,637 tokens.
Download SKILL.mdSave it as
.claude/skills/platform-specs-and-validation/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- platform-specs-and-validation
- description
- Platform specs and publish validation — per-platform requirements and the validate-before-publish step for multi-platform fan-out. Use when fanning a post out to multiple platforms, when a post is getting rejected, when mapping per-platform postType/required fields, or to run the validate-before-publish step. Encodes the per-platform postType enums, required-field matrices, and media rules from the OpenAPI spec, and runs POST /posts/validate so a post lands correctly on every target. Uses the CHECK framework. The keystone the per-platform format skills point to. WoopSocial validates + publishes atomically and has no update endpoint; the agent maps fields and fixes spec violations, but human-judgment calls (disclosure truthfulness, privacy intent) stay with the person; metrics never fabricated. Distinct from the per-platform format skills (one platform's content) and scheduling-and-queue (timing).
- version
- 1.0.0
platform-specs-and-validation
The cross-cutting publish-readiness skill — make a post correct on every target (required fields, media rules, limits) and run the validate-before-publish loop. It's the keystone the format skills point to. The agent maps fields + fixes spec violations + validates; WoopSocial validates and publishes; content craft and human-judgment calls stay elsewhere.
The POV: publish-ready, atomically, the first time
WoopSocial validates and publishes atomically — POST /posts checks every target together, and if
any one fails, nothing is created. There's no update endpoint, so a post that publishes wrong can't
be patched (edit = delete + recreate). That makes getting every target's fields right before
publish the whole game: the right postType, the required per-platform fields, the media rules, and
account-specific values (Pinterest board, TikTok privacy) resolved from platform-inputs — then
POST /posts/validate to catch what's left. This skill is where the format skills come to make sure it
will actually go through.
The framework: CHECK
(Depth: references/the-check-framework.md.)
- C — Collect the targets + project: list the social accounts; confirm they're in the same project; note each platform's field set.
- H — Hydrate per-platform required fields: fill each target's required fields (FB/IG
postType; TikTok's eight; YouTubetitle+privacy; PinterestpinterestBoardId); resolve account values fromGET /social-accounts/{id}/platform-inputs. - E — Enforce media + content rules: FB no image+video mix; IG Stories need media; Pinterest single
media; TikTok PHOTO/VIDEO field applicability; use
contentOverrideor separate posts where fan-out conflicts; respect text limits. - C — Confirm truthful declarations:
isBrandedContent/isYourBrand/madeForKidsare truthful declarations, not validation knobs — never flip them to clear an error; these stay with the person. - K — Knock it through validation:
POST /posts/validate→ fix all errors, review warnings → create (atomic). No update → delete + recreate (only whileNOT_STARTED).
The spec (ground truth — verify-quarterly)
Per-platform postType enums + required-field matrices + media rules + the platform-inputs discovery
endpoint + lifecycle facts (atomic create, no update, delivery status, schedule types):
references/woopsocial-publish-spec.md. The validate-then-create loop, the full ValidationField code
table + CreatePostErrorCode list + worked examples: references/validation-reference-and-recipes.md.
(The live OpenAPI spec / tools/integrations/woopsocial.md are the source of truth; enums and limits move.)
Honest scope (never violate)
- This skill ensures publish-READINESS (fields/media/spec correct + validated) — it doesn't write or improve the creative (the format/content skills do) and can't guarantee performance.
- WoopSocial validates + publishes atomically; one failing target fails the whole post. No update →
delete + recreate (only while
NOT_STARTED). - Disclosure/compliance declarations stay truthful (
isBrandedContent/isYourBrand/madeForKids) — never flipped to pass validation; privacy intent + disclosure truthfulness stay with the person. - Resolve account values (board, privacy) from
platform-inputs— don't guess. Never fabricate metrics — native analytics only. (Scope, distinctions + connections:references/scope-and-connections.md.)
Show full SKILL.md (204 more words)Show less
Distinct from its siblings (route correctly)
platform-specs-and-validation (this) = the cross-platform field/media/validation layer that makes a post
publish-ready on every target · the per-platform format skills (tiktok-photo-mode,
tiktok-video-publishing, threads-post, youtube-publishing-and-metadata, carousel-writer, …) =
craft one platform's content and point here for validation · scheduling-and-queue = timing/cadence,
not correctness · tools/integrations/woopsocial.md = the shared integration guide this applies post-level.
Where this connects
Receives from: every format skill (crafted content + chosen postType) and content-calendar (the
plan). Resolves with: GET /social-accounts/{id}/platform-inputs (boards, privacy options) + the
integration guide. Hands to: scheduling-and-queue → WoopSocial (POST /posts after isValid),
then webhooks/delivery status for confirmation. Supports: cross-platform-repurposing (per-target
contentOverride), analytics-and-reporting (native delivery readout), experimentation (valid
variants). Content craft + truthful declarations stay with the format skills + the person.
Definition of done
Every target collected and confirmed in one project; each target's required fields hydrated (postType /
privacy / board / disclosure / title as applicable) with account-specific values resolved from
platform-inputs; media + content rules enforced (no FB mix, IG-Story media, single Pinterest media, TikTok
field applicability) with contentOverride or separate posts where fan-out conflicts; disclosure/madeForKids
declarations left truthful (never flipped to pass); POST /posts/validate run with all errors resolved and
warnings reviewed before an atomic create; edits handled via delete+recreate, nothing fabricated and no
promised performance; correctly distinguished from the per-platform format skills and scheduling-and-queue.
© social-media-skills, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 5 other files (references) in skills/platform-specs-and-validation of social-media-skills/skills.
- SKILL.md
- evals/evals.json
- references/scope-and-connections.md
- references/the-check-framework.md
- references/validation-reference-and-recipes.md
- references/woopsocial-publish-spec.md
Open the folder on GitHubat commit 6e30eeb
Compare with similar skills
Platform Specs And Validation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Platform Specs And Validation this skillsocial-media-skills/skills | 134 | — | ~1.6k | Automated safety check: Pass | MIT | |
| ToolJet Marketplace Plugin BuilderToolJet/ToolJet | 41k | — | ~2.1k | Automated safety check: Pass | AGPL-3.0 | |
| Step Partsearthtojake/text-to-cad | 19k | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| OpenAPI to MCP Servermcp-use/mcp-use | 11k | — | ~5.2k | Automated safety check: Pass | Apache-2.0 | |
| Use Yaakmountain-loop/yaak | 19k | — | ~1.9k | Automated safety check: Pass | MIT | |
| API DesignerJeffallan/claude-skills | 12k | 1 repos | ~2k | Automated safety check: Pass | MIT |
Similar skills
Step Parts
earthtojake/text-to-cad
Find, evaluate, and download common purchasable CAD parts from step.parts, including named off-the-shelf actuators, servos, motors, electronics boards, connectors, screws, bolts, nuts, washers…
OpenAPI to MCP Server
mcp-use/mcp-use
Turns an OpenAPI or Swagger spec into an MCP server with the mcp-use TypeScript SDK, mapping each operation to a tool, wiring auth, testing and deploying.
Use Yaak
mountain-loop/yaak
A skill your agent uses when the user mentions Yaak, a Yaak workspace, or the yaak command, or asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API requests for reuse or manual…
API Designer
Jeffallan/claude-skills
Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.
CLI Creator
huangruiteng/CS-Notes
Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script.
More from social-media-skills/skills
All 106 skills in this repoAI Image Editing
social-media-skills/skills
The AI image-editing router — inpainting/object removal, background removal, upscaling, outpainting, old-photo restoration, and retouch, routed task-first to the right engine.
AI Music And Sound
social-media-skills/skills
The AI music + sound-design skill for social -- original/licensed audio beds and sound design for Reels/TikToks/Shorts/videos.
AI Search Optimization
social-media-skills/skills
A skill your agent uses to get a brand and its content CITED and RECOMMENDED by AI answer engines — the GEO (Generative Engine Optimization) / AI-search-visibility skill.
AI Video
social-media-skills/skills
The model-agnostic AI-video router and brief — the counterpart to image-prompt.
AI Voiceover
social-media-skills/skills
The AI narration / voiceover mini-skill (ElevenLabs-led). An agent skill from social-media-skills/skills.
Analytics And Reporting
social-media-skills/skills
Social media analytics and reporting — read native platform data honestly and turn it into next actions.
Related
Categories
Questions about Platform Specs And Validation
What does Platform Specs And Validation do?
Platform specs and publish validation — per-platform requirements and the validate-before-publish step for multi-platform fan-out. Platform Specs And Validation is an agent skill from social-media-skills/skills. Platform specs and publish validation — per-platform requirements and the validate-before-publish step for multi-platform fan-out.
When should I use Platform Specs And Validation?
Platform Specs And Validation fits situations like: fanning a post out to multiple platforms; A post is getting rejected; mapping per-platform postType/required fields; run the validate-before-publish step.
How do I install Platform Specs And Validation in Claude Code?
Run `npx skills add social-media-skills/skills --skill platform-specs-and-validation -a claude-code`. Or copy the skill folder (skills/platform-specs-and-validation in social-media-skills/skills) into .claude/skills/platform-specs-and-validation in your project. Claude Code loads it when a task matches its description.
How do I install Platform Specs And Validation in Codex?
Run `npx skills add social-media-skills/skills --skill platform-specs-and-validation -a codex`. Or copy the skill folder (skills/platform-specs-and-validation in social-media-skills/skills) into .agents/skills/platform-specs-and-validation in your project. Codex loads it when a task matches its description.
Can I use Platform Specs And Validation in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add social-media-skills/skills --skill platform-specs-and-validation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/platform-specs-and-validation, .gemini/skills/platform-specs-and-validation, .github/skills/platform-specs-and-validation and .opencode/skills/platform-specs-and-validation in your project.
What does Platform Specs And Validation need to run?
SKILL.md names no scripts, command-line tools or credentials: Platform Specs And Validation is instructions for the agent only.
Does Platform Specs And Validation access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Platform Specs And Validation safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Platform Specs And Validation use?
Platform Specs And Validation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Platform Specs And Validation use?
About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.9k tokens, read only when the agent opens those files.
What are the alternatives to Platform Specs And Validation?
Skills that share tags, products or a category with Platform Specs And Validation: ToolJet Marketplace Plugin Builder (ToolJet/ToolJet, 41k stars), Step Parts (earthtojake/text-to-cad, 19k stars), OpenAPI to MCP Server (mcp-use/mcp-use, 11k stars) and Use Yaak (mountain-loop/yaak, 19k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Platform Specs And Validation?
social-media-skills (a GitHub organization) maintains it in social-media-skills/skills, which has 134 GitHub stars. The repository holds 106 skills in this directory. The repository was last updated on October 1, 2026.
Source: social-media-skills/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.