Agent Skills turn repeated prompts into reusable, inspectable workflows.
This collection includes five small skills for work that comes up often when building with OpenCode or Claude Code: reviewing public copy, checking text limits, capturing public webpages as PDFs, sending task notifications, and structuring research for later use.
The full index is available at Published Agent Skills.
For OpenCode, Skills can live in ~/.config/opencode/skills/ or project-level locations supported by your setup. Claude Code can discover Skills from .claude/skills/. Put a Skill folder in the right location, restart the agent session if needed, and it becomes available when the task matches its description.
1. AI Writing Detector Skill
AI Writing Detector Skill reviews English and Brazilian Portuguese copy for patterns that make AI-written text feel generic.
It checks common issues such as repeated sentence rhythm, filler phrases, excessive formatting, and em-dash use. It also ships with a CLI and MCP server for text and file linting.
Useful prompts:
Review this README introduction with the anti-ai-tells Skill. Keep the technical facts, flag generic wording, and suggest direct replacements.
Run the writing linter on this release post, then rewrite only the passages that need attention.
This is useful before publishing documentation, launch posts, landing pages, and changelogs.
2. Text Counter Skill
Text Counter Skill gives exact counts for characters, words, sentences, paragraphs, lines, graphemes, bytes, and phrase occurrences.
It helps when "roughly under the limit" is not enough.
Useful prompts:
Write a 155-character meta description for this package and verify its exact character count.
Reduce this GitHub issue title to 80 characters without removing the error code.
Count the phrase "OpenCode" in this Markdown file.
The Skill makes counting rules explicit. That avoids surprises with spaces, Unicode characters, emoji, or repeated phrases.
3. HTML to PDF Skill
HTML to PDF Skill converts authorized public webpages into readable, browser-rendered PDFs.
The workflow uses Playwright and Chromium, waits for page assets, handles common cookie dialogs, removes ad blocks, and records the source URL and access time in each PDF footer.
Useful prompts:
Capture these public API documentation pages as PDFs for offline review.
Create a readable PDF copy of these public release notes and verify the page count.
This is practical for research, design reviews, long documentation pages, and internal reading packs.
4. ntfy Skill
ntfy Skill sends safe completion, failure, or blocked notifications for agent tasks that may take longer than 30 seconds.
It encourages a simple rule: estimate task duration before starting. If the work may take a while, notify the user once when it finishes or needs input.
The Skill keeps tokens out of repositories, shell history, URLs, and notification content. It supports ntfy.sh and approved self-hosted ntfy servers.
Useful prompts:
This export may take several minutes. Use the ntfy Skill to notify me once the final files are ready.
Before sending an ntfy message, confirm the token comes from the operating system credential store.
5. Open Knowledge Format Skill
Open Knowledge Format Skill creates source-linked Markdown research bundles for people and agents.
A bundle can include an index, a research report, an AI summary, source tables, evidence tables, and related output files. It separates facts from interpretation and points claims back to their sources.
Useful prompts:
Package this research into an OKF bundle with source links, evidence rows, caveats, and open questions.
Create an
ai_summary.mdthat another agent can use to continue this investigation safely.
This helps when research needs to survive longer than one chat session.
A Small Workflow That Works
A developer can combine these Skills in a normal agent session:
- Research a topic and save findings with the Open Knowledge Format Skill.
- Draft documentation or a blog post.
- Use Text Counter for title, description, and social-post limits.
- Run AI Writing Detector before publication.
- Capture public references as PDFs when visual records matter.
- Use ntfy for long-running exports, tests, or browser tasks.
No large framework is required. Each Skill is a focused Markdown file with optional scripts where automation adds value.
Top comments (0)