@profile-as-code/cli 0.2.0 → 0.3.5

package/skills/kofi/research/SOTA-2026.md

@@ -0,0 +1,160 @@
+# SOTA Ko-fi — research versionado (2026-10-05)
+
+Research date: 2026-10-05 (UTC). Same date for every source (each URL fetched
+2026-10-05). Tags: `[OFICIAL]` = Ko-fi's own docs/pages (primary) · `[WEB]` =
+primary URL fetched (incl. via mirror) · `[BENCHMARK]` = real-profile
+observation · `[?]` = not calibratable / not documented.
+
+Method / caveats: discovery ran through Ko-fi's own help-center search API
+(`help.ko-fi.com/api/v2/help_center/articles/search.json`, en-US, all 120
+articles) plus direct fetches. `ko-fi.com` and `help.ko-fi.com` pages are
+Cloudflare-challenged for plain HTTP fetch (HTTP 403); public page content was
+verified through a headless reader mirror (`r.jina.ai/<url>`) and marked
+`[WEB]`. `developers.ko-fi.com` does not resolve (NXDOMAIN) — Ko-fi documents
+webhooks, not a management API ([OFICIAL S18]).
+
+## 1. Bio/text fields on a Ko-fi creator page
+
+| Field (official UI name) | Where it appears publicly | Limit | Source |
+|---|---|---|---|
+| Display name / creator page label — "Buy a Coffee for {Name}"; browser `<title>` = "Buy {Name} a Coffee" | Profile header card, first element under cover | [?] no documented limit found | [OFICIAL S2] [WEB S12] |
+| Bio / About text — Ko-fi calls it "your bio" (onboarding step) and "bio text" (Content Guidelines §4); shown inside the **About** tab | First content block of the About tab, with a "Show more" collapse | [?] no documented limit found (search evidence below) | [OFICIAL S2, S8] |
+| Creator **status** ("Set a status" next to profile picture) | On your Ko-fi page next to your name, at checkout, and in DMs | **40 characters max**, emoji supported | [OFICIAL S1] |
+| **Social links** ("Your social links") | Rendered as icon anchors inside the **About** section of your profile | **Up to 15 links**; full `https://` URL required; recognized platforms get icons | [OFICIAL S3] |
+| Cover image (not text, same hero zone) | Top of page | 3:1 ratio, ideally 1200×400 px, under 8 MB, JPEG/PNG; not GIF | [OFICIAL S5] |
+| Social preview (OG) image + text ("Set your preview image and text") | Link preview on social platforms only, not the page itself | Image 2:1 or 600×300 px recommended; text customizable via "Customize preview"; auto-generated by default | [OFICIAL S4] |
+| Membership **standard terms** (not bio) | Pre-signup terms | **10,000 characters max** — the only bio-area text field with a Ko-fi-documented limit found | [OFICIAL S16] |
+| Tier Description / Welcome Message / Thank-you message (memberships & payments) | Tier card / post-payment surfaces, not on the public page | [?] | [OFICIAL S16, S10] |
+
+"No documented limit found" evidence for bio/About: full-text searched the
+whole help center (all 120 articles) for `page description`, `bio`,
+`About you introduce yourself`, `About me section add text to page`,
+`username change page name`; read in full: Get started (S2), Set your status
+(S1), Setting up your social links (S3), Change your social preview (S4),
+Cover image (S5), QR code (S6), Page Unpublished (S7), Content Guidelines
+(S8), Creating posts (S14), Polls (S15), Webhooks/API (S18), How do I get
+paid (S10), Memberships (S16). No article documents a character limit for the
+bio/About field → treat as unbounded-but-unknown; hard-validate nothing,
+soft-cap only. [?]
+
+## 2. Formatting of the About/bio text
+
+- The WYSIWYG toolbar (styling, links, embeds, images) is documented for
+  **Posts** (feed/blog), not for the profile bio: "Use the toolbar to control
+  the styling of your text and layout, add links, embed videos and images". [OFICIAL S14]
+- For the **bio/About card itself**: no documented markup support found (no
+  markdown/HTML mention in any read article) → write **plain text**. [?]
+- On a live page (ko-fi.com/webby), the About text rendered as one plain-text
+  run; the email inside the bio was NOT rendered as a clickable anchor, while
+  the social links right below (bio page, X, YouTube, Twitch, TikTok) were
+  real anchors. Bio lines longer than a few lines collapse behind "Show
+  more". [BENCHMARK/WEB S12]
+- **Links:** the official way to link out from the About zone is the
+  Social-links feature (up to 15, anchored with icons), not inline links in
+  the bio. Custom/unrecognized sites show a standard link icon; several
+  custom links drop into a dropdown. [OFICIAL S3]
+- **Line breaks:** no official statement; on S12 the creator's bio was a
+  single run visually — assume breaks not guaranteed. [?]
+- **Emoji:** explicitly supported in status ("Yes, you can add an emoji
+  alongside your custom status text"); Ko-fi copy itself uses emoji in bios
+  on marketing pages. [OFICIAL S1] — `[?]` for the bio field itself.
+
+## 3. URL / identity
+
+- Canonical pattern: `https://ko-fi.com/<username>`, with subpaths `/tiers`,
+  `/shop`, `/commissions` (official list in S9; observed also `/gallery`,
+  `/posts`, `/goal`). Help pages use `ko-fi.com/<em>yourusername</em>`. [OFICIAL S9, S16]
+- "Claim" language: Ko-fi's own copy — "claim your free page" (sign-up CTA);
+  the handle is chosen at claim time. [OFICIAL S10]
+- Rename: "you can change your Ko-fi username any time, and your QR code will
+  still work and link to your page" [OFICIAL S6]. Observed consequence: old
+  handle paths keep resolving — one creator's page served identical content
+  at both ko-fi.com/webby and ko-fi.com/peterwebby (same profile id);
+  profiles are also internally addressable by opaque id. [WEB S12][BENCHMARK]
+  → **rename-drift risk**: a pasted bio/URL may carry a stale handle; always
+  verify which handle is live before pasting.
+- Social preview can retain an old/dead name after rename (help labels it
+  "deadname"; fix = re-generate preview in Page settings). [OFICIAL S4]
+- Privacy/unpublish: pages have **no documented self-service hide/unpublish
+  setting**. "Unpublished" = Ko-fi-side suspension (strikes/three-strike
+  system; Trust & Safety review). Page-level **NSFW tag** exists. [OFICIAL S7, S8]
+- Host nuance: `kofi.com` (no hyphen) and `www.kofi.com` **do not resolve at
+  all** (DNS lookup `ENOTFOUND`, 2026-10-05). Only `ko-fi.com` serves pages —
+  identity URLs and handle checks must use the hyphenated host. [WEB S17]
+
+## 4. Visibility / SEO
+
+- robots.txt: `User-agent: *` disallows only `/Administration/`, `/Manage/`,
+  `/api/`, `/design-system/`, `/streamalerts/overlay`(+animated/goaloverlay).
+  Creator pages `/<handle>` are **not disallowed** → crawlable by default.
+  [WEB S11]
+- Public search/directory: `ko-fi.com/explore` renders the logged-out landing
+  (no browsable creator directory/search in that path); Ko-fi states post
+  tags "are not for searches now, but will be handy when we improve the tag
+  function". No public profile-search is documented in the help center. [WEB S13] [OFICIAL S14] [?]
+- Documented discoverability: none beyond external promotion. Ko-fi actively
+  bans "mass SEO abuse (commercial spam)" pages. [OFICIAL S8]
+
+## 5. GEO (LLM citability) — observed on one real page [WEB]
+
+- Fetched ko-fi.com/webby (and its duplicate at /peterwebby) through a
+  headless reader: `<title>` "Buy Peter Webby a Coffee"; tab nav **About |
+  Membership | Gallery | Posts | Shop**; an **"About"** section heading
+  containing the creator's bio text with a "Show more" collapse; social-link
+  anchors; tier cards. An LLM/agent with a JS-capable fetcher can read the
+  full About text as rendered HTML. [BENCHMARK/WEB S12]
+- Caveat: the page is a client-side app; whether the raw no-JS HTML contains
+  the resolved About text **was not verified** (direct fetch Cloudflare-blocked
+  403; server-side proxies failed) → [?]. The platform is Cloudflare-hostile
+  to plain HTTP fetchers; GEO checks should use a browser-rendered fetcher and
+  expect ~403 on raw requests. [WEB S12]
+
+## 6. Deploy (manual paste flow) — dashboard paths [OFICIAL unless noted]
+
+- Account-level: **Settings** (sidebar) → **Profile** tab
+  (`ko-fi.com/settings?tab=profile`): display name + "Your social links"
+  (add/remove, Save). [OFICIAL S3]
+- **Settings → Page** tab (`ko-fi.com/settings?tab=page`): "Set your preview
+  image and text" → "Customize preview"; **Page focus** dropdown (default
+  landing tab: Feed/Memberships/Shop/Commissions); custom color;
+  coffee-counter toggle. [OFICIAL S4, S16]
+- Your page: **`ko-fi.com/manage/mypage`** → top-right three-dots → "Set
+  Cover Image"; About content lives on the page's **About** area ("Your
+  about page > Add Something" pattern per the Posts/Polls articles). [OFICIAL S5, S14, S15]
+- Status: page → "Set a status" next to profile pic → text (≤40) + emoji +
+  "Clear after" → Save. [OFICIAL S1]
+- Paste-checklist reference order: name → status → bio/About text → social
+  links → preview text/image → page focus → cover image.
+
+## 7. Short vs long bios
+
+- The page loads half-way down the cover image "so that your visitors can get
+  straight to your main content" — the About text is on the default (About)
+  tab and truncated behind "Show more" when long. [OFICIAL S5] [WEB S12]
+- The only guaranteed short-slot line is the **status** (≤40 chars) next to
+  the name (also at checkout and in DMs). [OFICIAL S1]
+- Link shares are governed by the customizable social preview text/image,
+  independent of the About text. [OFICIAL S4]
+- No documented per-field limit for About → the engine treats About as
+  unbounded, with renderer/skill-side soft caps. [?]
+
+## Sources (all fetched 2026-10-05 UTC)
+
+- S1 https://help.ko-fi.com/hc/en-us/articles/39075030682269-Set-your-status (API: help.ko-fi.com/api/v2/help_center/en-us/articles/39075030682269.json)
+- S2 https://help.ko-fi.com/hc/en-us/articles/360014098514-Getting-started-on-Ko-fi
+- S3 https://help.ko-fi.com/hc/en-us/articles/32432965286557-Setting-up-your-social-links
+- S4 https://help.ko-fi.com/hc/en-us/articles/360020081893-Change-your-social-preview-image-and-text
+- S5 https://help.ko-fi.com/hc/en-us/articles/360004243378-Make-your-page-stand-out-with-a-cover-image
+- S6 https://help.ko-fi.com/hc/en-us/articles/28740826348701-Your-Ko-fi-QR-code
+- S7 https://help.ko-fi.com/hc/en-us/articles/360010484497-What-does-Page-Unpublished-mean-and-what-should-I-do
+- S8 https://help.ko-fi.com/hc/en-us/articles/360007937553-Ko-fi-Content-Guidelines (unpublish/ban, "bio text", SEO abuse, NSFW tag)
+- S9 https://help.ko-fi.com/hc/en-us/articles/115004002614-Adding-a-Ko-fi-Button-to-your-WordPress-site-or-blog (URL patterns)
+- S10 https://help.ko-fi.com/hc/en-us/articles/115003980093-How-do-I-get-paid ("claim your free page")
+- S11 https://ko-fi.com/robots.txt
+- S12 https://ko-fi.com/webby and https://ko-fi.com/peterwebby (fetched via r.jina.ai mirror; direct fetch HTTP 403)
+- S13 https://ko-fi.com/explore and https://ko-fi.com/FAQ (via r.jina.ai mirror)
+- S14 https://help.ko-fi.com/hc/en-us/articles/360007638073 (Creating posts; WYSIWYG toolbar; "tags… not for searches now")
+- S15 https://help.ko-fi.com/hc/en-us/articles/19068973151133-Create-a-Poll-on-Ko-fi ("Your about page > Add Something")
+- S16 https://help.ko-fi.com/hc/en-us/articles/4402945994001-Ko-fi-Memberships-and-Membership-Tiers (terms 10,000 chars; tier Description/Welcome Message; Settings > Page)
+- S17 DNS checks: `kofi.com`, `www.kofi.com`, `developers.ko-fi.com` → getaddrinfo ENOTFOUND (fetch attempts 2026-10-05)
+- S18 https://help.ko-fi.com/hc/en-us/articles/360004162298-Does-Ko-fi-have-an-API-or-webhook (webhooks = payments only; manage at ko-fi.com/manage/webhooks)

package/skills/linkedin/post.md

@@ -0,0 +1,50 @@
+# LinkedIn post — skill (MVP)
+
+> Week-1 post skill. The machine-readable limits live in `posting.yaml`; this file
+> is the judgment layer the agent reads before writing. Sources are dated in
+> `posting.yaml`; re-verify before making a hard claim.
+
+## What a LinkedIn post is for
+
+One idea, one reader, one reason to keep reading. The post is not a profile
+summary: it is a claim or a story that earns the next line. Write for a specific
+audience from `positioning.audiences`; do not write for "everyone".
+
+## Shape
+
+1. **Hook** — the first 1–2 lines carry the whole post. A concrete tension,
+   observation or result; no throat-clearing ("En el mundo de…").
+2. **Body** — 2–5 short paragraphs. One idea per paragraph. Concrete nouns,
+   dates, numbers, links from the SSOT. Use `{{fact:...}}` for every fact.
+3. **Close** — a question, an invitation or a next step. No rage-bait, no
+   "comenta SÍ" engagement farming.
+
+## Rules
+
+- **Length:** 3,000 characters max (LinkedIn's current limit; see
+  `posting.yaml` sources). Aim for 900–1,800 — the ceiling is not the target.
+- **Links:** only from `identity.links`, `projects[].links`,
+  `publications[].url`, `credentials[].verifyUrl` or `artifacts[].locator.url`.
+  Do not invent or shorten a URL.
+- **Hashtags:** 3–5 maximum, only if they are how the audience searches.
+- **Facts:** never paraphrase a date, number, DOI or URL. Cite with
+  `{{fact:<pointer>}}`; the engine renders it and fails on a dangling pointer.
+- **Voice:** first person, direct, no hype. Match `brandVoice` (tone, values,
+  avoid); the post should sound like the person, not like a content template.
+
+## Anti-patterns
+
+- A hook that could belong to any post in the niche.
+- A list of achievements without a claim.
+- "I'm humbled to announce" / "Excited to share" openings.
+- A link dump; a post is not a newsletter.
+- Hashtag stuffing.
+
+## Output contract
+
+Save one text block per variant at `posts/<seed>/linkedin/linkedin-<n>.md`, then
+record it:
+
+```
+pasco post choose <seed> --channel linkedin --variant linkedin-1
+```

package/skills/linkedin/posting.yaml

@@ -0,0 +1,23 @@
+# linkedin post rules — machine-readable (MVP)
+#
+# The `post check` command reads limits/settings/hashtags from here. The prose
+# strategy lives in post.md; this file is the contract. Re-verify the source
+# before changing a hard limit.
+
+platform: linkedin
+settings:
+  __type: linkedin
+limits:
+  maxChars: 3000
+links:
+  policy: identity-ssot-only
+hashtags:
+  max: 5
+structure:
+  - hook
+  - body
+  - close
+sources:
+  - url: https://www.linkedin.com/help/linkedin/answer/a528565
+    date: 2026-10-20
+    note: "LinkedIn post character limit (3,000); re-verify, the platform changes limits."

package/skills/x/post.md

@@ -0,0 +1,46 @@
+# X post — skill (MVP)
+
+> Week-1 post skill. The machine-readable limits live in `posting.yaml`; this file
+> is the judgment layer the agent reads before writing. Sources are dated in
+> `posting.yaml`; re-verify before making a hard claim.
+
+## What an X post is for
+
+One sharp claim, observation or link. X rewards the first line and punishes
+context-free threads. The post is a projection of the seed, not a summary of the
+profile.
+
+## Shape
+
+1. **Hook** — one line, concrete, no "🧵" unless the thread is real.
+2. **Body** — 1–2 short lines. One idea. If it does not fit, the seed is a
+   thread, not a post; the MVP writes single posts, so cut.
+3. **Close** — optional link or question; do not bait replies.
+
+## Rules
+
+- **Length:** 280 characters for standard accounts (see `posting.yaml` sources;
+  verified/premium accounts have a different ceiling — do not assume).
+- **Links:** only from the SSOT. X may shorten visually; the URL you write must
+  be the canonical one.
+- **Hashtags:** 0–3, only if they are how the audience searches. No stuffing.
+- **Mentions:** only handles that are real and relevant; do not invent or
+  mass-mention.
+- **Facts:** cite with `{{fact:<pointer>}}`; never invent a number, date or URL.
+- **Voice:** first person, direct, no hype. Match `brandVoice`; the post should
+  sound like the person, not like a growth account.
+
+## Anti-patterns
+
+- "A thread 🧵" on a single post.
+- Engagement bait ("like if you agree").
+- A link with no claim.
+- Hashtag stuffing; emoji spam.
+
+## Output contract
+
+Save one text block per variant at `posts/<seed>/x/x-<n>.md`, then record it:
+
+```
+pasco post choose <seed> --channel x --variant x-1
+```

package/skills/x/posting.yaml

@@ -0,0 +1,24 @@
+# x post rules — machine-readable (MVP)
+#
+# The `post check` command reads limits/settings/hashtags from here. The prose
+# strategy lives in post.md; this file is the contract. Re-verify the source
+# before changing a hard limit.
+
+platform: x
+settings:
+  __type: x
+  who_can_reply_post: everyone
+limits:
+  maxChars: 280
+links:
+  policy: identity-ssot-only
+hashtags:
+  max: 3
+structure:
+  - hook
+  - body
+  - close
+sources:
+  - url: https://developer.x.com/en/docs/x-api/v2/tweets/create-post
+    date: 2026-10-20
+    note: "X post character limit (280 for standard accounts; verified/premium differ)."