tin-computer/tin/search-and-answer-engines
Claude Code and agent skill by tin-computer/tin
- community
Checking that the SKILL.md file is still in the repository.
Shape a planned article so search engines and AI answer engines can find, quote and cite it, without changing what the evidence supports.
Install
npx vskill@latest install tin-computer/tin/search-and-answer-enginesSKILL.md
Structure for search and answer engines
Apply these rules with the planned-content skill when the outcome is draft for an article or an answer page; a page refresh follows the page-refresh skill instead. They shape the copy; they never outrank accuracy, the brief, the editorial judgment or the writing guide. Where a rule would weaken the page, leave it out rather than forcing it.
For an update, keep the destination's structure, headings and anchors. Apply these rules only to the sections you change; do not add an FAQ or rename existing headings on a page you update.
Page shape
- The article file still starts with its
#title and carries no frontmatter or search
listing; delivery writes the site's header. An answer page is the one exception: its two-line search listing comes first, as the answer-page section of the prompt says. The title is the buyer's question or its direct answer, in plain words.
- Answer first: the paragraph after the title answers the question in 40 to 60 words, names
the options when there are several, and still makes sense when quoted on its own.
- Question headings: when a section answers a question the buyer asks next, phrase its
##
heading as that question, ending with a question mark, and open the section with one or two sentences that answer it.
- Comparison table: when the page compares two or more products, plans or approaches, add a
Markdown table with one row per option and columns for the facts a buyer compares (price, what it does, limits, who it suits), every cell backed by a cited source.
- FAQ, where it fits: when buyers will have follow-up questions the body does not answer, add
## FAQ with three to five ### questions, each ending with a question mark and answered in two to four sentences.
## Sourceslast: cite inline, linking the sentence that carries each claim, and list every
cited source again at the end. Never pad the list with sources the page does not use.
Readability
- Keep sentences under 25 words on average and paragraphs under 100 words.
- Use lists for steps, options and criteria, and the table for side-by-side facts.
- Define a term the first time the page uses it. Prefer the words buyers use in their
questions.
- Write for a reader who skims: every heading and the first sentence of every section carry
meaning without the rest of the page.
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingcodex_procedures/content.generate/skills/search-and-answer-engines/SKILL.md
Popularity
- 7-day trend score
- 5
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/tin-computer/tin/search-and-answer-engines)