Skip to content
Back to skills

Content Factory

ASecurity

Both natures. The field of publishing — channels on social networks, blogs, boards and forums, the voices of authors, the numbers every publication brings back, the topics that rise. The facts the method of shape-the-need weighs when a person's goal involves publishing, and how the work runs once the person chose its shape. Load it together with shape-the-need, never instead of it.

  • 69 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 18, 2026
ai-agentsgonodeawsgitapi

Works with

  • cli
  • api

Security analysis

A100/100

Scanned November 18, 2026

npx -y skills add Fractera/Agentic-Engineering-Infrastructure --skill content-factory --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Content Factory?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Content Factory
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/fractera-content-factory-web4-node-starter-kit/badge)](https://www.skillsdirectory.com/skills/fractera-content-factory-web4-node-starter-kit)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: content-factory
description: "Both natures. The field of publishing — channels on social networks, blogs, boards and forums, the voices of authors, the numbers every publication brings back, the topics that rise. The facts the method of shape-the-need weighs when a person's goal involves publishing, and how the work runs once the person chose its shape. Load it together with shape-the-need, never instead of it."
---

# The field of publishing

**Process: both.** The talk is the working process; whatever is born goes through `create-element` or the hand's own agent (build).
Node step 658; the owner, 2026-11-05: «обычно пользователи используют чистый Claude.ai для того чтобы везти свои социальные сети … но
можно достигнуть раза до больших результатов если таким образом использовать Fractera …». Step 673: this skill gives the facts of the
field; which shape the work takes — an answer, a route, a hand of its own, a boundary, the network — the method of `shape-the-need`
decides on the node's facts.

## Why it matters
Claude.ai alone writes a good post. Publishing is a loop — a channel, a voice, the numbers of each publication, the topic that rises —
and each publication can teach the next only where the loop is kept.

## The facts the forces act on
- **A platform** has its own account, API, rules on automation, spam and limits, and its own rhythm. Its rules are read on its own
  pages, never told from memory (`npm run site-rules`, skill `provider-rules`). Platforms, their accounts and their rhythms are routes,
  records and calendar entries of ONE publishing hand of one owner — never a hand each: a platform is not a boundary (force 5 of
  `shape-the-need`). A hand of its own only where force 5 differs — another owner's accounts, money or secrets, a face of its own.
- **A voice** — an author's style taken apart into as many components as possible — serves every channel that writes in it (force 4).
  It is built from the author's open texts that `site-rules` allows, or from what the person brings (CLAUDE.md §6: a site that forbids
  study gives only the person's screenshots); we take the techniques, never the texts.
- **The numbers** — every publication returns its statistics through the platform's official API; reading them and changing the next
  publication is what makes the loop grow (force 6). They belong to the one who publishes.
- **A rising topic** is seen through the official APIs and feeds of networks, channels, video and news portals, on a clock (force 6).
- **Media the node lacks** — image or video generation, montage, animation — is a capability many will reuse (force 4).
- **The person's own domain** can hold their long texts, besides the platforms; `npm run find` and the cards show which hand's area
  already covers a site.

## The platforms, read on their own pages (node step 751, 2026-11-15 — read again before building; prices change)
- **LinkedIn** — posting through the official product «Share on LinkedIn» (scope `w_member_social`), free; its User Agreement (effective
  2025-11-03, section 8.2) forbids «bots or other unauthorized automated methods» to create, comment on, like, share or re-share posts,
  sharing log-in credentials and copying cookies; no official way to read other people's feeds.
  https://www.linkedin.com/legal/user-agreement · https://learn.microsoft.com/en-us/linkedin/consumer/integrations/self-serve/share-on-linkedin
- **X** — pay per request, no subscription: a post $0.015, a post with a URL $0.20, a read $0.005 per post. https://docs.x.com/x-api/getting-started/pricing
- **Instagram** — Meta's publishing API, free; at most 100 published posts per 24 hours (a carousel counts as one).
  https://developers.facebook.com/docs/instagram-platform/content-publishing
- **YouTube** — Data API, free within the quota: 100 `videos.insert` and 10 000 units a day for the rest; a list costs 1 unit, a comment
  50. https://developers.google.com/youtube/v3/determine_quota_cost
- Not yet read: LinkedIn statistics of personal posts by API; Instagram's account requirements and replies to comments; X's automation
  rules on likes.

## The assistant and the person's own account — what to promise
The owner, 2026-11-15: «если я всё-таки открою LinkedIn и попрошу тебя написать пост как мой помощник ты имеешь право это сделать … или
это мой выбор? … чтобы если я обещаю это пользователям то они могли это сделать».
- **Writing is always allowed** — a draft in the person's voice, any network. Using an assistant to write is the person's choice.
- **Publishing**: by the platform's official API after the person's yes — or the agent puts the draft into the platform's composer in the
  person's Chrome and the PERSON presses «Опубликовать». The press stays theirs.
- **The agent pressing «Post», liking or commenting in the person's browser** is the automation LinkedIn's section 8.2 forbids; the rule
  binds the account holder, the price is their account (restricted or closed). Name the rule and the price once and offer the two lawful
  ways (skill `provider-rules`); never promise users automated likes, comments or browser posting.
- Likes and comments on other people's posts: a morning digest in Telegram with links and draft comments; the person acts from the phone.

## Serving others — partners, clients (step 765)
- Each partner is another owner (force 5 of `shape-the-need`): their own subscription sign-in, accounts, voices and numbers; their
  platforms are routes. Several people on one platform share nothing but the platform — the method never joins them.
- What is the person's goes with the person: their list of networks and their watch — a research of anything, their own networks and
  the accounts they follow first. What is heavy and shared stays apart: image and video generation, montage (the owner, 2026-11-16:
  «сам факт что это в его или нет в отличие от например генерации видео и изображений»).
- Images, video, montage, avatars — heavy, reused by all, the operator's own (force 4): called over i2i in a live queue; the queue and
  its limits are not built — a `need` when the first factory asks.

## How the work runs once the shape is chosen — one link at a time, each after the person's yes
1. **The channels and the goal**, in the person's words: which networks, blogs, boards, forums; what the publications are for.
2. **Whatever is new is born with its horizon** (`create-element`, its area and what it may grow into); a new job of a field a hand
   holds is a route built by that hand's own agent.
3. **A portrait** — the style taken apart (`study-for-element`), then adapted to the person's product.
4. **A publication** — the one who holds a channel asks the one who holds the voices for a text, over the API the two agents agree
   (`route-to-element`, i2i). The person approves a draft, or gives a standing yes for one channel and one rhythm.
5. **The numbers** — read into the publisher's own tables and the deep memory (node step 654: its own space); an analysis at a rhythm
   the person chose says what works where — the topic, the format, the hour, the voice — and proposes the next changes.
6. **The topics** — the one who watches proposes a publication in trend to the channel that fits.
7. **Community skills** for posting and analytics — `skills_find` first.

## Laws
- Every publication, every posting rhythm and every round of watching starts after the person's yes; a resident process is named with
  its price in memory.
- Official APIs, feeds and the person's own accounts only.
- No tool of the node posts by itself today: the hand that holds a channel builds its publishing on that platform's API.
- The followers' personal data never goes into git; nothing is offered as working that the node cannot do today.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.