best-practices
Use when current practice or outside evidence can change a decision: comparing approaches, libraries, or patterns against the user's constraints.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- best-practices
- description
- Use when current practice or outside evidence can change a decision: comparing approaches, libraries, or patterns against the user's constraints.
- allowed-tools
- WebSearch, WebFetch, Read, Glob, Grep, Skill
- argument-hint
- <topic>
- user-invocable
- true
03 SKILL.md 正文
Given a topic, you have to search online for the best, high quality, updated information about it, using critical thinking and reasoning by first principles. Save your searches result to a temporary file on the user system and if you are a subagent, tell to the main agent the path of those files so he can read them in detail.
On technical topics, take evidence only from top sources, not SEO stuff or AI slop:
- official documentations and specifications
- maintainer posts, authoritative engineering blogs, peer-reviewed papers
- widely adopted github projects that are still actively maintained (ideally > 2k stars and last commit < 3 weeks ago)
Age each claim against its own horizon: weeks for versions, APIs, pricing, limits, and advisories; months for tool and library choices; years for architecture, patterns, and concepts. An old source holds when the idea still holds. Say why it holds, and confirm that no newer source replaced it. Mark what you cannot confirm as unverified.
Cite material claims inline, and separate evidence from inference. Explain consensus, disagreement, uncertainty, and where each recommendation applies. State what evidence would overturn your recommendation. Recommend for the user's goals and constraints, not for an imaginary average user.
If missing context changes the answer, ask for it or give clearly conditional recommendations. Do not pad the report with source quotas, evidence labels, or weak secondary material.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.