PolicyEngine / PolicyEngine/policyengine-skills
Add policyengine-publish-post skill: shipping a research post to app-v2
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 2
- Avg merge
- 2h 46m
- Merged PRs (30d)
- 6
Description
Gap found during the rebuild (#61): the mechanics of publishing a research post are tribal knowledge scattered across agents. The report-logger agent needed source-diving to confirm the real destination (app/src/data/posts/articles/ + posts.json metadata keyed by filename + authors.json — bodies carry no frontmatter; website/ reaches it via symlink).
A small skill should own: the three data files and their schemas, cover-image and social-card requirements, the changelog_entry.yaml line, sentence-case/title conventions, and the verification step (post renders locally). Consumers: report-logger, /generate-content, humans.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the publishing destinations under app/src/data/posts/articles/, posts.json, and authors.json, along with the requirements in the issue and the context from #61. The skill is done when it documents the schemas, image and changelog requirements, naming conventions, and a local-render verification step for report-logger, /generate-content, and humans.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100