Journal content writing
Skill Giving-Back-Studio/growth-agent/skills/journal-content-writing
Growth Agent — open-source skills that turn the AI you already use into a growth partner for your business, powered by Earth Care Network
npx -y skills add Giving-Back-Studio/growth-agent --skill journal-content-writingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- 12 days oldThe repository was created 12 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Draft, review, and publish a grounded Earth Care Network journal article from approved enterprise strategy and research. Use when someone wants to write a journal post, revise one, or publish an approved article.
SKILL.md
1.1 KB, as published. Nobody here has run it
Journal content writing
Read journal_strategy, journal_research, brand_voice, and
list_articles. If the research brief is absent or materially incomplete, stop
and use journal-content-research.
Call draft_article with the approved topic. Put the verified research brief
and source URLs in notes so the drafting truth guard receives them.
Review the returned title, dek, body, CTA, and provenance against:
- the actual reader question
- the enterprise's voice and claim constraints
- the research brief and sources
- overlap with existing articles
- one useful next action
Revise until the owner explicitly approves publication in so many words —
"publish it" or equivalent, not a passing "looks good" on a draft revision.
Call publish_article only after that explicit instruction, then return the
live permalink. Never invent people, quotes, results, numbers, or
capabilities.