lilmgenius/polysona · Archived

status

Show current persona health and content pipeline status

Installation

$ npx skills add lilmgenius/polysona --skill status

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from lilmgenius/polysona.

npx skills add lilmgenius/polysona

Browse all from lilmgenius/polysona

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 154
License LICENSE
Default branch ralphthon
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,736 B
  • docs SUMMARY.md 69 B

History

  1. First recorded snapshot · 4 installs

SKILL.md

!ACTIVE=$(cat personas/_active.md 2>/dev/null || echo "default"); ls personas/ 2>/dev/null && echo "---" && cat "personas/$ACTIVE/persona.md" 2>/dev/null && echo "---" && cat "personas/$ACTIVE/nuance.md" 2>/dev/null && echo "---" && cat "personas/$ACTIVE/accounts.md" 2>/dev/null && echo "---" && ls content/trends/ 2>/dev/null | wc -l && echo "trend files" && echo "---" && ls content/drafts/ 2>/dev/null | wc -l && echo "draft files" && echo "---" && ls content/qa/ 2>/dev/null | wc -l && echo "qa files" && echo "---" && ls content/published/ 2>/dev/null | wc -l && echo "published files"

Status Skill Protocol

Display a quick system status snapshot:

  • Active personas count
  • Last interview footprint from persona context
  • Trends, drafts, QA reports, and published content counts
  • Pipeline readiness status (interview -> trend -> content -> qa -> publish)

Guardrails

  • Only report facts grounded in the loaded files.
  • Do not invent psychology frameworks, audience segments, or pipeline components that are not explicitly present.
  • If framework coverage is partial, list only the exact framework names that appear in interview-log.
  • If the missing frameworks are not explicitly named in the files, report only the missing count.
  • Do not infer the category or identity of missing frameworks from the global project spec.
  • Treat GAP or summary rows as log entries, not as substitute names for missing psychology frameworks.
  • If a section is missing, say it is missing instead of inferring completion.
  • Prefer exact counts from content/trends/, content/drafts/, content/qa/, and content/published/ over assumptions.