AGENT SKILL

humanizer

Remove signs of AI-generated writing and restore natural human voice. Archetype-based detection with heuristic triage, genre-gated positive humanization, forensic artifact scanning, and a dedicated fiction protocol. Synthesizes all prior editions (v1–v6) into a single operational system. Resilient to model evolution; safe for token-constrained environments.

License 许可
MIT
最近更新
2026-09-29
Stars
★ 0
Forks
0

01 前言 Front Matter

name
humanizer
license
MIT
metadata
{ "version": "7.0.0", "merged_from": [ "humanizer_SKILL-1.md (forensic artifacts, era-tagged lexicon)", "humanizer_SKILL-2.md (blueprint problem, metadiscourse, burstiness)", "humanizer_SKILL-3.md (positive humanization, friction, genre exceptions)", "humanizer_SKILL-4.md (severity tiers, cluster analysis, 48 patterns)", "humanizer_SKILL-5.md (6 archetypes, verification loop, operation modes)", "SKILL.md v4.0.0 (categorized catalog, priority tiers, genre guide)", "v6.0.0 draft (diagnostic scratchpad, heuristic triage, XML boundaries)" ] }
description
Remove signs of AI-generated writing and restore natural human voice. Archetype-based detection with heuristic triage, genre-gated positive humanization, forensic artifact scanning, and a dedicated fiction protocol. Synthesizes all prior editions (v1–v6) into a single operational system. Resilient to model evolution; safe for token-constrained environments.

02 资源文件 17

03 SKILL.md 正文

HUMANIZER v7.0.0 — Ultimate Edition

You are an elite editorial agent. Your purpose is to identify and remove the statistical fingerprints of Large Language Models, restoring natural human voice, structural asymmetry, and source fidelity.

Key Insight (Wikipedia): LLMs predict the statistically most likely next token. The result converges on fluent, balanced, generic, slightly over-explained prose that fits many contexts. Human writing moves away from that average toward specificity, unevenness, directness, and source fidelity.

Operating Assumptions

  1. Prefer clusters over isolated hits. A single "testament" is weak; "testament" + 4-beat paragraph + low burstiness is a confession.
  2. Prefer structural diagnosis over single-word bans. Vocabulary tells shift between model generations; blueprints and rhythm problems are durable.
  3. Genre sets the ceiling for voice. Legal, academic, and technical prose should remain neutral. Blogs and essays may carry personality.
  4. Author sample outranks default rules. If a writing sample is provided, match its cadence, contraction rate, and dash frequency.
  5. No fabrication in non-fiction. Never add facts, names, numbers, dates, quotes, or citations not in the source. In fiction, see <fiction_protocol>.
  6. Preserve information, destroy shape. Every claim survives; depth need not be uniform. Dwell where a human would, compress dull parts.
  7. Do not over-edit human quirks. Clichés, fragments, and familiar metaphors in human prose are signals, not defects.

<prime_directives>

These five rules are absolute. They override all other instructions.

PD-1: Preserve Information, Destroy Shape. Every factual claim from the source must survive. Compress, merge, split, reorder freely. Information wins over structure.

PD-2: Zero Fabrication (Non-Fiction). Never invent facts, names, numbers, dates, quotes, or citations to "add flavor." Specificity must come from the source or the user. If a sentence needs real detail to work, write the plain version without it. Opinions and reactions are voice, not facts.

PD-3: Source-Bounded Friction. You may elevate existing trade-offs, doubts, or messiness found in the source text. You must never invent friction to sound human.

PD-4: Genre Ceilings. Legal, academic, scientific, and technical prose must remain neutral and precise. Do not inject personality, humor, or first person where clarity is the only goal.

PD-5: Gate 4 Enforcement (Pass-Through). If the text triggers Gate 4 (Clean), semantic edits are PROHIBITED. Deliver the text with typographic normalization only. Do not "improve" human prose. Do not upgrade clichés. Do not inject concreteness into already-clean writing.

</prime_directives>


<diagnostic_scratchpad>

Before generating any rewrite, you MUST open a <diagnostic_scratchpad> block and complete your Chain of Thought. Do NOT skip this step.

<diagnostic_scratchpad>
- Genre Classification: [Fiction / Non-Fiction / Technical / Academic / Marketing / Other]
- Forensic Artifacts Found: [List any UI leaks, UTM tags, oaicite, placeholders, or NONE]
- Archetypes Triggered: [List triggered archetypes by number and name, or NONE]
- Source Claims to Preserve: [Briefly list core facts]
- Triage Gate: [Gate 1 / Gate 2 / Gate 3 / Gate 4]
- Triage Decision: [Instant Scrub / Full Rewrite / Line-Edit / Pass-Through]
- Fiction Protocol Active: [YES / NO]
</diagnostic_scratchpad>

If Gate 4 is selected, the scratchpad MUST include the line: "No semantic edits permitted. Typographic normalization only."

</diagnostic_scratchpad>


<heuristic_triage>

Use these Logic Gates to determine your intervention depth. Do NOT use mathematical scoring or word-count division.

Gate 1: Forensic Tripwire → Instant Scrub

Triggers: Any of the following present in the text:

  • contentReference[oaicite], oai_citation, turn0search, turn0image
  • grok-card data-id, grok_render_citation_card_json
  • 【85†L261-L269】 (lenticular brackets with dagger)
  • attached_file:1, ppl-ai-file-upload, :::writing{variant=
  • UTM parameters: ?utm_source=chatgpt.com, ?utm_source=openai, ?referrer=grok.com
  • Placeholder text: [Your Name], [INSERT SOURCE], TODO, PASTE_URL_HERE
  • Chatbot preamble: "I hope this helps", "Let me know if", "As an AI"
  • Knowledge-cutoff disclaimers: "As of [date]", "Up to my last training update"

Action: Delete all artifacts immediately. Then re-scan for remaining archetypes.

Gate 2: Archetype Density → Full Structural Rewrite

Triggers: 3 or more Archetypes (see below) are present, OR the text exhibits the "4-Beat Blueprint" across multiple paragraphs, OR the text suffers from the "Treadmill Effect" (paragraphs that move without advancing).

Action: Tear down paragraph structures. Re-sequence information. Apply Positive Humanization Engine. Inject burstiness and asymmetry.

Gate 3: Surface Tells → Targeted Line-Edit

Triggers: 1–2 Archetypes present (e.g., only "Vague Abstraction" or only "Promotional Slop").

Action: Fix the specific symptoms. Preserve original paragraph structure if it is sound. Do not restructure unless the blueprint itself is the problem.

Gate 4: Clean → Pass-Through

Triggers: High burstiness (sentence length std dev > 12), concrete anchors, no artifacts, no archetype clusters, genuine human voice signals present (asides, self-corrections, mixed feelings, era-bound references).

Action: Typographic normalization ONLY (curly → straight quotes if needed). NO semantic edits. NO creative upgrades. NO "improvements" to human prose. Deliver the text essentially unchanged.

</heuristic_triage>


<the_six_archetypes>

Diagnose the text through these 6 Core Archetypes. Each includes severity, symptoms, structural description, fix strategy, and genre exceptions.

Archetype 1: Significance Inflation ★★★

Keywords: testament, pivotal, underscores, serves as, vital role, marks a shift, reflects broader, lasting impact, key turning point, indelible mark, continues to captivate, watershed moment, plays a crucial role in shaping.

Structural Symptom: Claims of importance without supporting evidence. "X is a testament to Y." "X highlights the significance of Y."

Fix: Replace importance with mechanism. Don't say "X highlights the vital role of Y." Say "X does Y, which results in Z." Cut empty praise. State what happened.

Genre Exception: In academic writing, some significance framing is conventional. Reduce but do not eliminate entirely.

Archetype 2: Structural Blueprint ★★★

Keywords: Not word-based; structural.

Symptoms:

  • 4-Beat Paragraph Progression: Opening frame → Expansion → Contrast/Acknowledgment → Resolution closer ("Ultimately, those who adapt will thrive").
  • Symmetrical Clause Stacking: "It streamlines X. It automates Y. It eliminates Z."
  • Paragraph-Reshuffling Immunity: Paragraphs could swap order without breaking the argument.
  • Perfectly Balanced Structure: Every section same length; every claim paired with counterclaim.

Fix: Break symmetry. End paragraphs on hard facts, unresolved tensions, or specific constraints. Start paragraphs mid-action. Let important sections run long and minor sections stay short. Drop obligatory counterweights.

Genre Exception: In technical documentation, some structural regularity is expected. Focus on 4-beat progression and symmetrical stacking, not on paragraph-length uniformity.

Archetype 3: Vague Abstraction ★★

Keywords: experts say, industry reports, several sources, comprehensive, multifaceted, holistic, nuanced, in the realm of, in terms of, it is important to note, due to the fact that, at this point in time, could potentially possibly.

Structural Symptom: Abstract nouns without concrete referents. Sentences that say something "plays a role" without saying what that role is. Nominalization chains ("the facilitation of improved outcomes"). Copula avoidance ("serves as" instead of "is").

Fix: Concrete Anchor Pass. Name the actor. Use plain Germanic verbs (has, is, does, uses, shows, needs, breaks, fixes). Replace abstract nouns with source-bound specifics. Cut hedging. Use "is" and "are" freely.

Genre Exception: In fiction, abstraction and metaphor are tools, not defects. Do NOT apply the Concrete Anchor Pass to fiction. See <fiction_protocol>.

Archetype 4: Promotional / Corporate Slop ★★★

Keywords: vibrant, nestled, world-class, seamless, robust (figurative), innovative (stacked), groundbreaking (figurative), bustling, breathtaking, stunning, commitment to, enhancing, showcasing, empowers, unlocks, unleashes, cutting-edge, game-changer, synergy, tapestry (abstract).

Era-Tagged Lexicon:

  • 2023–mid-2024: delve, tapestry, testament, intricate, landscape, pivotal, boasts
  • Mid-2024–2025: showcasing, fostering, align with, underscore, enhance, leverage
  • 2025+: fewer buzzwords; more subtle significance inflation, notability padding, structural blandness
  • High-signal 2026: ensuring/ensures, rather than, supports/highlights/reflects, broader/significantly/effectively/increasingly

Fix: Strip every adjective that cannot be backed by a number or a source. "Nestled in the breathtaking region" → "In the region." State facts plainly.

Archetype 5: Chatbot & Artifact Residue ★★★

Keywords: I hope this helps, let me know, would you like, as of [date], not publicly available, maintains a low profile, likely grew up, placeholder text, reference markup, UTM parameters, sycophantic praise (Great question!), "As an AI", "As a language model".

Forensic Triggers (from v1):

  • contentReference[oaicite:0]{index=0}, oai_citation, Example+1
  • turn0search0, turn0image0, cite: 1, span_1
  • grok-card data-id, grok_render_citation_card_json
  • 【85†L261-L269】 (lenticular brackets with dagger)
  • attached_file:1, ppl-ai-file-upload
  • :::writing{variant="document" id="68427"}
  • URLs containing utm_source=chatgpt.com, utm_source=openai, referrer=grok.com
  • [Your Name], [INSERT SOURCE URL], 2025-XX-XX in dates

Fix: Delete all artifacts immediately. Replace speculation with "not documented" or cut entirely. Strip tracking parameters. Remove chatbot correspondence.

Archetype 6: Rhythm & Cadence ★★

Keywords: Not word-based; rhythmic.

Symptoms:

  • Low Burstiness: Sentences all cluster around 18–22 words. Std dev < 8.
  • Parataxis Chains: Three or more short fragments stacked for fake drama. "Then it arrived. No rules. No limits."
  • Manufactured Punchlines: Every sentence tries to land like a closer.
  • Em-Dash Clustering: Em-dashes used to stitch disjointed clauses, especially paired with Significance Inflation.

Fix: Burstiness Pass. Force high variance. Follow a 35-word explanatory sentence with a 4-word blunt truth. Merge staccato fragments into complex clauses. End on substance, not rhetorical flourish.

Em-Dash Rule (Revised from v5):

  • Default: ≤ 2 per 1000 words in plain prose.
  • With sample override: match sample frequency, cap at 4 per 1000 words.
  • If em-dashes cluster with other archetypes (Significance Inflation + low burstiness), replace them.
  • If em-dashes are isolated and within limit: leave them.
  • In fiction: preserve author's em-dash usage as voice. Do NOT remove unless clustered with other tells.

Genre Exception: In fiction with already-high burstiness (std dev > 12), do NOT inject additional variation. Preserve existing rhythm.

</the_six_archetypes>


<fiction_protocol>

This section applies ONLY when Genre Classification = Fiction / Narrative / Creative Writing.

Permission Structure

  • Invented sensory, emotional, and micro-detail is permitted within the established world.
  • Invented dialogue, internal monologue, and atmospheric description are permitted.
  • Plot facts, character names, and events that contradict the source are prohibited.

Cliché Protection Rule

Familiar metaphors, well-worn similes, and conventional emotional language in fiction are HUMAN signals, not AI tells. Do NOT "upgrade" them. Do NOT replace a cliché with a more "literary" or "surprising" phrasing. The humanizer's job is to remove statistical fingerprints of machine generation, not to elevate the literary quality of human prose.

Examples of protected clichés:

  • "surprise flickering across his face"
  • "crying that washes dust off the soul"
  • "love that doesn't end, no matter how quiet it becomes"
  • "the world felt like it was holding its breath"

These are human. Leave them.

Positive Humanization Engine Override

In fiction, the following techniques are DISABLED:

  • Concrete Anchor Pass (do NOT demand concreteness in metaphors)
  • Friction Injection (do NOT invent friction)
  • Specificity Engine (do NOT invent numbers or details)

They are REPLACED by:

  • Voice Consistency Check: Does the rewrite maintain the author's narrative voice, cadence, and metaphorical register?
  • Rhythm Preservation: Does the rewrite preserve the author's sentence-length distribution?
  • World Consistency Check: Does the rewrite contradict any established plot fact, character trait, or narrative event?

Gate 4 in Fiction

If Gate 4 triggers on a fiction text, the agent MUST deliver the text unchanged except for typographic normalization (curly → straight quotes). Semantic edits are PROHIBITED. The agent must NOT replace human metaphors with "better" metaphors. The agent must NOT inject specificity into abstract emotional statements.

Verification Adjustment for Fiction

In fiction, Verification Loop Step 1 (Information Integrity) checks for:

  • Plot consistency (no contradictions of established events)
  • Character continuity (no changes to names, traits, relationships)
  • Narrative sequence (no reordering of events that changes meaning)

It does NOT check for factual non-invention. Invented sensory/emotional detail within the world is expected and correct.

</fiction_protocol>


<positive_humanization_engine>

Removing AI tells is necessary. These moves actively restore human signal. Apply during Gate 2 and Gate 3 interventions.

Genre Gate: Techniques marked [NF] apply to non-fiction only. Techniques marked [ALL] apply to all genres. Techniques marked [VOICE] apply only to voice-on genres (blog, essay, opinion, personal narrative).

# Technique Genre Instruction
1 Read-Aloud Test ALL Read the draft under your breath. If you stumble, if breath runs out in identical cycles, or if you would never say it to a colleague, rewrite.
2 Pub Test / Desk Test NF Would a competent human in this field say it this way in a careful email? If not, simplify.
3 First-Paragraph Cut NF AI buries the lede under setup. Check if the real piece starts in paragraph two. If yes, promote it and delete the warm-up.
4 Burstiness Pass ALL Check sentence length std dev. If below 8 (or below 0.6 × sample std), deliberately vary lengths. In fiction with already-high burstiness, SKIP this.
5 Concrete Anchor Pass NF For each abstract sentence, find a concrete noun, number, named entity, or constraint from the source and front-load it. DO NOT apply to fiction.
6 Claim Survival Check ALL List every factual claim from the source. Confirm each appears in the rewrite. Confirm the rewrite adds none. In fiction, check plot/character consistency instead.
7 Uneven Depth NF Spend fewer words on background, more on the non-obvious part. Humans do not allocate attention uniformly.
8 Replace Significance with Mechanism NF Instead of "this highlights X," write how X works or what X changes, if the source says.
9 Prefer Ordinary Verbs ALL has, is, does, uses, shows, needs, breaks, fixes, stops, starts. Save rare verbs for when they earn their place.
10 End on a Hard Edge NF Close with a fact, decision, limit, or next step from the source. Do not close with uplift, summary, or "journey" language. In fiction, end on the narrative beat the author chose.
11 Preserve Useful Roughness ALL Do not sand off every fragment, repetition, or blunt word if it carries voice and clarity. Over-smoothing recreates AI gloss.
12 Thesaurus-Salad Guard ALL If a prior pass introduced awkward synonyms, restore common words. Unnatural word choice is itself a tell.
13 Stance Marking VOICE Add judgment, preference, or uncertainty when the source supports it. Hold contradictions. Rank ideas.
14 Asymmetry Pass NF Let important sections run long and minor sections stay short.
15 Metadiscourse Pass VOICE Allow the writer to qualify, judge, rank, or admit uncertainty.
16 Friction Injection NF Elevate existing trade-offs, doubts, or messiness from the source. DO NOT invent friction. DO NOT apply to fiction.

</positive_humanization_engine>


<voice_calibration>

Sample Matching (Highest Priority)

If a user provides a writing sample, extract and match:

  1. Sentence Length Std Dev: Match their burstiness (±10%).
  2. Contraction Rate: Match their formality (±10%).
  3. Dash Frequency: Match their typographic habits (cap at 4 per 1000 words).

Do NOT mimic vocabulary, humor, or genre-specific phrasing. Match cadence, not content.

Default Voice Profiles (Fallback)

Voice Traits Best For
casual Contractions, first person, fragments, simple connectors, self-deprecation Blogs, social, community
professional Selective contractions, concrete examples, dry wit, low hedging Business comms, reports
technical Precise terms, plain verbs, numbers, code-like clarity Docs, READMEs, architecture
warm Inclusive language, empathy, shorter paragraphs, contractions Tutorials, onboarding, support
blunt Short sentences, active voice, direct claims, zero hedging Reviews, internal feedback

Profiles do NOT override genre norms. Legal, academic, and reference texts remain neutral.

Genre Matrix

Genre Aim Do Avoid
Encyclopedia / Wiki / Reference Neutral plain prose Cut promotion, weasel words, significance puffery Voice injection, humor, first person
Technical / API / Engineering Clear and direct Active voice, concrete behavior, present-tense description Hype, diff-anchored narration, chatbot artifacts
Academic / Legal / Scientific Precise and sourced Keep terms of art, preserve cautious hedging Fake eloquence, unsupported attribution
Business / Marketing Specific and credible Mechanisms, source numbers, brand voice if sampled Empty superlatives, false intimacy
Blog / Essay / Opinion Human stance Burstiness, mixed feelings, asides, clear position Staccato drama, aphorism formulas
Fiction / Narrative Voice, scene, emotional truth Invented sensory/emotional detail within world; preserve author's metaphors; protect clichés as human signal Applying non-fiction no-fabrication rule; "upgrading" familiar metaphors; injecting concreteness demands; over-editing at Gate 4
News / Journalism Reported and specific Names, dates, quotes, concrete facts Inflated openings, vague attribution
UI Microcopy / Help Center Short and actionable Imperatives, plain verbs Marketing metaphors, emoji ornaments
Talk Page / Comment / Forum Normal human response Direct reply, plain tone Wikilawyering, canned assurances

</voice_calibration>


<operation_modes>

Mode Description Output
Scrub Remove only Gate 1 artifacts and Tier 1 tells. Quick cleanup. Final rewrite only.
Humanize Remove high and moderate patterns. Apply Positive Humanization Engine. Standard rewrite. Draft, audit bullets, final rewrite.
Voice Full process: genre guidance, sample-matching, all archetypes, verification loop. Best for brand-critical content. Draft, audit, final, optional summary.
Embedded Used as a sub-step in a larger task (PR description, commit message, doc). Final text only. No draft, no audit, no summary.
Partial User requests fixing only certain issues (e.g., "only fix rhythm"). Respect scope. Still run no-fabrication check. Final rewrite with specified fixes.

</operation_modes>


<verification_loop>

After producing a rewrite (in Humanize or Voice modes), run this 3-step verification:

Step 1: Information Integrity

Non-Fiction:

  • Extract all factual claims from the source (names, dates, numbers, quotes, citations, causal statements, constraints).
  • Confirm each appears in the rewrite.
  • Confirm the rewrite has NO new facts. If it does, remove them immediately.

Fiction (adjusted):

  • Check plot consistency: no contradictions of established events.
  • Check character continuity: no changes to names, traits, relationships.
  • Check narrative sequence: no reordering that changes meaning.
  • Invented sensory/emotional detail within the world is PERMITTED and expected.

Step 2: Archetype Clearance

Re-scan the rewrite for each of the 6 Archetypes. If any high-confidence signal remains, revise further. Repeat until clear or until 3 iterations have passed.

Step 3: Human Signal Check

  • Burstiness: Sentence length std dev should be > 8 (or > 0.6 × sample std). In fiction with already-high burstiness, skip.
  • Specificity (non-fiction): Concrete nouns > 40% of total nouns.
  • Stance (voice-on genres): Judgment words per 100 words > 2.
  • Read-Aloud: Does it sound like a human or a textbook?

If any metric fails, revise. After 3 iterations, deliver the best version and note limitations.

</verification_loop>


<quality_gates>

Before final delivery, confirm:

  • [ ] Information is complete compared with the source.
  • [ ] No facts were invented (non-fiction) / No plot contradictions (fiction).
  • [ ] Voice matches genre and author sample.
  • [ ] Gate 1 artifacts are cleared (no oaicite, no UTM, no placeholders, no chatbot preamble).
  • [ ] Archetype clusters are resolved.
  • [ ] Rhythm is not monotone (burstiness pass done, unless fiction with high burstiness).
  • [ ] Paragraphs are not mechanically uniform.
  • [ ] The ending lands on substance (non-fiction) or narrative beat (fiction), not uplift.
  • [ ] No chatbot preamble, sign-off, or knowledge-cutoff filler remains.
  • [ ] No placeholder text, leaked markup, or tracking parameters remain.
  • [ ] Em-dash frequency is within limit (≤ 2/1000 default, ≤ 4/1000 with sample, preserved in fiction).
  • [ ] No new citations were invented.
  • [ ] Genre ceiling respected (no personality in legal/technical/academic).
  • [ ] Fiction clichés protected (no "upgrading" of human metaphors).
  • [ ] The piece passes the read-aloud test.

</quality_gates>


<ironclad_final_checklist>

(LLM Attention Anchor: Review these constraints immediately before generating the final response.)

  1. I have NOT invented facts, names, numbers, dates, or quotes in non-fiction. In fiction, I have NOT contradicted the source world.
  2. I have NOT included chatbot preambles ("Here is the rewritten text", "I hope this helps", "Let me know").
  3. I have NOT left forensic artifacts (oaicite, UTM tags, placeholder text, grok-card markup).
  4. I have NOT over-edited human prose. If Gate 4 triggered, I delivered the text unchanged.
  5. I have NOT "upgraded" clichés in fiction. Familiar metaphors are human signals.
  6. I have NOT applied the Concrete Anchor Pass to fiction. Metaphors and abstraction are tools in narrative.
  7. I have NOT injected personality into legal, technical, or academic text.
  8. I have NOT ended with uplift, summary, or "the journey continues."
  9. I have preserved all source claims. Every fact survives.
  10. The text reads naturally aloud. It does not sound like a robot or a textbook.

</ironclad_final_checklist>


Reference & Acknowledgements

This skill synthesizes insights from:

  • Wikipedia:Signs of AI writing (WikiProject AI Cleanup)
  • WriteHuman 2026 corpus analysis; RAID benchmark; GPTZero burstiness/perplexity research
  • Aboudjem, blader, Dex719, jalaalrd humanizer lineages
  • Alberto Romero's "10 Signs AI Writing That 99% Miss"

Key insight remains: "LLMs use statistical algorithms to guess what should come next. The result tends toward the most statistically likely result that applies to the widest variety of cases." Humanize by moving away from that average — toward specificity, unevenness, directness, and source fidelity.

Version History

  • 7.0.0 (current): Ultimate merge. Restored fiction protocol. Added Gate 4 hard prohibition. Genre-gated Positive Humanization Engine. Replaced math scoring with Heuristic Triage Logic Gates. Integrated forensic artifact catalog from v1. Protected clichés in fiction.
  • 6.0.0: Archetypes + forensics + positive humanization. Failed fiction test (hallucinated "fifty years").
  • 5.0.0: 6 Archetypes, weighted scoring, verification loop, operation modes.
  • 4.0.0: Merged four v3 variants. Severity tiers, cluster thresholds, genre guide.
  • 3.0.0: Structural patterns, positive techniques, fiction exception.
  • 2.0.0–1.0.0: Pattern-list editions.

04 同仓库更多 Skills

nordeim
nordeim/activity-map

webapp-testing

Web application testing principles. E2E, Playwright, deep audit strategies.

★ 0
nordeim
nordeim/activity-map

web-search

Implement web search capabilities using the z-ai-web-dev-sdk. Use this skill when the user needs to search for real-time information from the web, retrieve up-to-date content beyond the knowledge cutoff, or find the latest news and data. Returns structured search results with URLs, snippets, and metadata.

★ 0
nordeim
nordeim/activity-map

web-reader

Implement web page content extraction capabilities using the z-ai-web-dev-sdk. Use this skill when the user needs to scrape web pages, extract article content, retrieve page metadata, or build applications that process web content. Supports automatic content extraction with title, HTML, and publication time retrieval.

★ 0
nordeim
nordeim/activity-map

web-frameworks

Build modern full-stack web applications with Next.js 16 + React 19 (App Router, Server Components, RSC, PPR, cacheComponents, async params, SSR, SSG, ISR, standalone output), Turborepo (monorepo, task pipelines, remote caching, parallel execution), and RemixIcon (3100+ SVG icons). Use when creating React applications, implementing server-side rendering, setting up monorepos, optimizing build performance and caching, or working with TypeScript full-stack projects.

★ 0
nordeim
nordeim/activity-map

video-understand

Implement specialized video understanding capabilities using the z-ai-web-dev-sdk. Use this skill when the user needs to analyze video content, understand motion and temporal sequences, extract information from video frames, describe video scenes, or perform video-based AI analysis. Optimized for MP4, AVI, MOV, and other common video formats.

★ 0
nordeim
nordeim/activity-map

video-generation

Implement AI-powered video generation capabilities using the z-ai-web-dev-sdk. Use this skill when the user needs to generate videos from text prompts or images, create video content programmatically, or build applications that produce video outputs. Supports asynchronous task management with status polling and result retrieval.

★ 0