huashu-material-search_skill

This skill quickly searches 1800+ authentic posts for personal experiences and cases to add human touch and credibility to your content.
  • Python

49

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill alchaincyf/huashu-skills --skill huashu-material-search

  • SKILL.md10.6 KB

Overview

This skill searches a personal素材 library of 1,800+ real posts and opinions to add human detail and credibility to content. It surfaces short dynamics, curated theme entries, and rewrite guidance so you can convert raw posts into natural, story-driven paragraphs. Use it when content feels too "AI", when you need a real-case opener, or when articles require firsthand product impressions.

How this skill works

The skill supports two search modes: direct grep-style searches across the raw CSV of 1,800+ posts for freshest, original expressions, and filtered lookup in pre-extracted theme files for structured summaries. It ranks matches by relevance, returns source context and timestamps, and offers concrete rewrite tips to expand a short post into a full paragraph while preserving the original attitude. It also flags timeliness and data accuracy considerations.

When to use it

  • You need a real opening anecdote or hook for an article or script
  • An argument needs supporting real-world examples or user opinions
  • Draft reads too "AI" and needs authentic voice or blunt observations
  • You want product/tool first-hand impressions (pros, cons, pricing pain)
  • Preparing case studies, lessons learned, or concrete pitfalls to avoid

Best practices

  • Prefer direct search of raw CSV for new or niche topics to get original voice
  • Always rewrite: expand background, add time/scene, keep the original attitude
  • Preserve factual details (dates, tool names, figures) and don't invent
  • Use 1–2 personal素材 items per article—opening and a case/example is ideal
  • If unsure about a claim's current validity, mark it as "at the time" and re-verify

Example use cases

  • Write an article intro about Claude Code using a two-week hands-on post as a hook
  • Compare AI coding tools with side-by-side snippets of real impressions and price tradeoffs
  • Illustrate a product-development pitfall (e.g., missing docs in HarmonyOS) with a concrete anecdote
  • End an essay on programmers' future value with a short personal insight about judgment vs. coding
  • Transform short social posts into full paragraphs for a newsletter or video script

FAQ

Broaden keywords, try synonyms or higher-level concepts, or check the theme index; if none exists, proceed with analysis-only content.

Can I copy posts verbatim?

No. Always rewrite into longer prose, preserve attitude but avoid direct copy to protect original context and flow.

How do I know a素材 is still accurate?

Check the post timestamp in results and validate any product-specific claims; when in doubt, label the claim as 'at the time' or re-verify current status.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational