<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[veyvia]]></title><description><![CDATA[veyvia]]></description><link>https://veyvia.hashnode.dev</link><image><url>https://cdn.hashnode.com/uploads/logos/6aafde71faaa784e4ca0677b/10cf5771-3309-4ccb-ab51-155904121ac6.png</url><title>veyvia</title><link>https://veyvia.hashnode.dev</link></image><generator>RSS for Node</generator><lastBuildDate>Wed, 18 Nov 2026 15:17:00 GMT</lastBuildDate><atom:link href="https://veyvia.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[A walk through SkillHey Topics: writing, research, and documents]]></title><description><![CDATA[Most of the work I give an agent is not "write code". It is some mix of reading, drafting, and packaging: polish a paragraph without changing the claim…]]></description><link>https://veyvia.hashnode.dev/a-walk-through-skillhey-topics-writing-research-and-documents</link><guid isPermaLink="true">https://veyvia.hashnode.dev/a-walk-through-skillhey-topics-writing-research-and-documents</guid><category><![CDATA[AI]]></category><category><![CDATA[llm]]></category><category><![CDATA[Productivity]]></category><category><![CDATA[writing]]></category><dc:creator><![CDATA[jyjyxt]]></dc:creator><pubDate>Sun, 15 Nov 2026 05:22:16 GMT</pubDate><content:encoded><![CDATA[<p>Most of the work I give an agent is not "write code". It is some mix of reading, drafting, and packaging: polish a paragraph without changing the claim, gather sources, turn the result into a deck or a document someone else can open. Those jobs share a vocabulary — "write this", "look this up", "make a doc" — and that vocabulary is exactly what used to send me to the wrong skill.</p>
<p>This is a walk through three lanes on <a href="https://skillhey.com/topics">SkillHey Topics</a>: writing, research, and documents. SkillHey is a curated library of 1,000+ AI agent skills, arranged first by the job you want to do. Each skill page includes a description, the source repository, when the repository was last updated, the install command, and the agents each author lists, such as Claude Code, Codex and Cursor. I am part of the SkillHey team, and I use these pages the same way I would recommend a colleague use them: start with the task, then open a path.</p>
<h2>Writing: protect the thing you cannot afford to lose</h2>
<p>The <a href="https://skillhey.com/topics/writing">Writing</a> lane is easy to treat as a single box. It is not. Editing, technical documentation, academic prose, translation, narrative, and summarization all produce text, but they fail in different ways. A skill that is good at tightening sentences may still rewrite a term of art. A skill that is good at a repository guide may be the wrong choice for a paper.</p>
<p>I start by naming what must stay intact. Sometimes it is terminology. Sometimes it is voice. Sometimes it is structure, or the scope of the evidence. Then I pick a path.</p>
<p>Nature Polishing is a useful example of that constraint written into the skill itself. It is described as a way to polish or translate academic prose while preserving facts, terminology, numerical precision and the scope of the evidence. If my job is the opposite of that — for example, writing a short AGENTS.md for a repository — I go elsewhere. AGENTS.md Guidance is there to create or revise concise, repository-specific instructions, which is a different writing problem.</p>
<p>When the work is closer to line editing, I open <a href="https://skillhey.com/topics/editing-and-proofreading">Editing &amp; Proofreading</a>. When it is closer to docs, I open <a href="https://skillhey.com/topics/technical-writing">Technical Writing &amp; Docs</a>. The point is not to memorise skill names. The point is to stop asking one writing skill to protect every quality at once.</p>
<h2>Research: decide whether you need sources, a deep pass, or a check</h2>
<p>Research has the same trap. "Look this up" can mean a market scan, a long reading pass, academic source work, or a fact check. If I leave that unspecified, I tend to pick a general research skill and hope it covers the case.</p>
<p>The <a href="https://skillhey.com/topics/research">Research</a> lane on Topics is split into market and competitor research, deep research, academic research, and fact-checking. I use the sentence I wrote earlier to choose among them. A comparison of products is not the same job as reading papers, and neither is the same as checking a specific claim.</p>
<p>The path pages make that split concrete. <a href="https://skillhey.com/topics/deep-research">Deep Research</a> is for going out across the web and coming back with sources; Last30Days, for example, looks at recent discussions across Reddit, X, YouTube, Hacker News, GitHub and similar places. <a href="https://skillhey.com/topics/academic-research">Academic Research</a> is closer to papers: Nature Paper Card builds a structured reading card covering methods, evidence chains, limitations and testable ideas, and Academic Deep Research is described as forming questions, searching and checking literature, then producing a referenced report. <a href="https://skillhey.com/topics/fact-checking">Fact-Checking</a> is a smaller path; Nature Reference Verifier cross-checks bibliographic details and reports inconsistencies.</p>
<p>I still read the skill page before installing. Research skills can differ in the sources they expect you to provide, the format of the output, and the agents the author lists. The path only gets me to a short list. The page tells me whether a given skill wants me to bring papers, URLs, or a question, and what it intends to produce.</p>
<h2>Documents: the output format is the decision</h2>
<p>After the writing or research is done, I usually have to hand something over. That is where I used to get sloppy. I would look for "document skills" and install the first familiar name.</p>
<p>The <a href="https://skillhey.com/topics/documents">Documents</a> lane makes the format the first choice. Its paths cover conversion and reports, presentations, PDF, Markdown, Word, OCR, and spreadsheets. If the next artefact is a talk, I go to <a href="https://skillhey.com/topics/presentations">Presentation &amp; Slides</a>. Frontend Slides builds animated HTML presentations, with visual previews and an option to turn an existing PowerPoint file into a web deck. Codex PPT turns articles, reports, papers and outlines into a visually consistent PPTX.</p>
<p>If the artefact is a spreadsheet, Excel Spreadsheets focuses on explicit assumptions, consistent formulas, formatting and recalculation checks. If it is a styled page from Markdown, Markdown to HTML converts the source and keeps code, math and diagrams. These skills sit in the same lane because they all deal with documents. They are separated because the file you will send is not the same.</p>
<h2>How the three lanes connect</h2>
<p>A realistic week for me looks like this. I start in Writing or Research, depending on whether I already have the material. I keep one constraint in mind — a term, a claim, a source type. When the draft is stable, I move to Documents and name the file I need to deliver. Only then do I install a skill from that path.</p>
<p>The Topics hub is the map for that movement. It will not tell me that a skill is the right one for my draft. It will, however, keep me from treating "writing", "research" and "documents" as a single search query. If you work in the same mix of prose, sources and files, try picking the lane before you pick the skill, and see whether the shortlist gets easier to read.</p>
]]></content:encoded></item></channel></rss>