Token导航 LogoToken导航

Agent Skill · 研究检索

style-forensics(风格取证)

style-forensics 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

style-forensics 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为执行命令;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 67,721。

总安装 242周安装 10GitHub Stars 37下载 79核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:style-forensics(风格取证)
来源仓库:https://github.com/majesticlabs-dev/majestic-marketplace
仓库路径:skills/style-forensics
安装命令:
npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill style-forensics
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill style-forensics

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

style-forensics 用于查找、检索和筛选相关信息。适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词、任务场景或来源线索快速定位候选结果时使用。通过 npx skills add 命令从指定仓库安装,具体用法需结合 README 进一步确认。

安装前建议确认权限范围、维护状态及是否涉及联网、命令执行或文件读写操作。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/style-forensics

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要执行命令,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

style-forensics 怎么安装?

在终端执行 npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill style-fore…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

style-forensics 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

style-forensics 需要什么权限?

权限级别是执行命令。安装流程涉及命令执行,可能通过 npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill style-forensics 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

style-forensics 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

style-forensics 用的人多吗?

公开数据是累计安装 242 次,近一周安装 10 次,下载 79 次,GitHub 37 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

style-forensics 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 需要执行命令,装到常用环境前要先评估影响面。
  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 不能接受 Skill 在你机器上执行命令的人。
  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
style-forensics

风格取证 · 本页

24237执行命令未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Style Forensics

Analyze: $ARGUMENTS

Audience: Writers and content creators who need a precise, measured voice fingerprint for use with style-writer and humanizer.

Goal: Extract quantitative style metrics from writing samples and produce a Style DNA report. Measure, don't guess.


Phase 1: Extract Prose

Strip the file to prose only before measuring anything. Remove:

  • Code blocks (...)
  • Inline code (replace with "CODE")
  • Headings (lines starting with #)
  • Blockquotes (lines starting with >)
  • Horizontal rules (---)
  • Metadata lines (tags, bylines, dates)
  • URLs inside markdown links (keep link text)

Save the cleaned prose to a temp file for all subsequent analysis.

Report: Total prose word count.


Phase 2: Sentence Metrics

Extract individual sentences from the prose. Handle:

  • Decimal numbers (don't split on "4.5")
  • Abbreviations (e.g., i.e.)
  • Quoted strings containing periods

Measure and report:

MetricHow
Total sentencesCount
Average sentence lengthwords / sentences
Median sentence lengthMiddle value of sorted lengths
Min / MaxExtremes
Short sentence ratio% of sentences under 8 words
Sentence length distribution4 bands: 1-7, 8-15, 16-25, 26+ words with counts and percentages

Describe the rhythm pattern: How do short and long sentences alternate? Do short sentences cluster? Are long sentences followed by punchy landings?


Phase 3: Punctuation DNA

Count across the full prose text:

MarkMeasure
CommasTotal and per 100 words
SemicolonsTotal and per 100 words
ColonsTotal and per 100 words
Em dashes (— and –)Total
Exclamation marksTotal
Parenthetical asidesTotal, per 100 words, list each one
Rhetorical questionsTotal, per 100 words, list each one

Identify the punctuation fingerprint: Which marks carry the structural load? What's absent? Note any unusual ratios (e.g., colon-to-semicolon ratio).


Phase 4: Paragraph Structure

MetricHow
Total prose paragraphsCount (exclude pure list paragraphs)
Average paragraph lengthWords
One-sentence paragraph ratio% of paragraphs with 0-1 sentence-ending punctuation

Phase 5: Vocabulary Profile

MetricHow
Total wordsCount alpha-only tokens
Unique wordsCount distinct
Lexical diversityunique / total
Long words (8+ chars)Count and percentage
Common word ratio% that are top-100 English function words
Top 15 long wordsWith frequency counts

Describe the vocabulary character: Academic or accessible? Jargon-heavy or plain? Are key terms repeated deliberately (thematic anchoring) or is vocabulary varied?


Phase 6: Tone Profile

POV and Address

  • Count I/my/me instances (per 100 words)
  • Count we/our instances (per 100 words)
  • Count you/your instances (per 100 words)
  • Determine dominant POV

Hedging Language

Search for: probably, perhaps, maybe, might, could be, I think, kinda, sort of, likely, arguably, roughly, nearly, pretty, fairly, basically, genuinely, honestly, admittedly, I guess, I don't think

Report total, per 100 words, and each instance. Note whether hedges appear on claims, predictions, or data.

Emotional Register

  • Profanity count and context for each instance
  • Exclamation marks (already counted)
  • Describe the overall temperature: restrained, casual, intense, breathless?

Contractions

  • Total count and per 100 words
  • Top 10 most frequent

Phase 7: Signature Devices

Search for and quantify each of these patterns. Not all will be present. Report what IS there and what IS NOT.

Sentence openers

  • Top 15 opening words with counts
  • Conjunction openers (And/But/Or/So): total count, percentage of all sentences, breakdown by word

Fragment patterns

  • List all sentences under 6 words ending in a period
  • Identify fragment stacking (2+ consecutive fragments)
  • Identify single-word sentences

Recurring structures

Search for:

  • "That's..." landing sentences
  • "Here's..." launcher sentences
  • "The [noun] is/was..." authoritative declaratives
  • "Not X. Y." contrast patterns
  • "I just..." casualness markers
  • "Let me..." gear-shift cues
  • "Same with X." stacking
  • Credential references ("I've built/seen/written...")
  • Direct persuasion ("believe me," "face it," "let's be honest")
  • Any other repeated phrase pattern that appears 3+ times

Rhetorical devices

  • Anaphora / repetition patterns
  • Rhetorical question clusters (2+ questions in sequence)
  • Colon setup-payoff structures
  • Historical framing / analogy patterns

Temporal markers

  • Count temporal words (first, then, next, eventually, now, started, etc.)
  • Describe the temporal architecture: chronological? thematic? diary-style?

Phase 8: Structural Blueprint

Describe the macro-structure:

Opening pattern

How does the piece begin? (Bold thesis? Scene setting? Credential stack? Anecdote?)

Body organization

How are sections structured internally? What's the repeating unit?

Closing pattern

How does the piece end? (Call to action? Honest concession? Restatement? Promise?)


Phase 9: Compile the Report

Write the full Style DNA report as a markdown file saved next to the source file, named [source-filename]-style-dna.md.

The report MUST include:

  1. Header with source file, word count, date analyzed
  2. Measured Metrics table (all numbers from phases 2-4)
  3. Sentence Length Distribution table
  4. Vocabulary Profile table with top words
  5. Tone Profile section (POV, hedging, emotional register)
  6. Signature Devices section (only devices that actually appear, with counts and examples)
  7. Structural Blueprint section
  8. Quick Reference Card (code block with all key numbers for at-a-glance use)

If analyzing multiple files by the same author, add a Cross-Article Comparison section with a comparison table and analysis of which traits are stable fingerprints vs. sliding dials.


Execution Notes

  • Run all independent measurements in parallel (sentence analysis, punctuation counts, vocabulary analysis can run simultaneously)
  • Use Python for accurate counting. Shell one-liners are fine for simple counts but Python handles sentence splitting and edge cases better.
  • Do not round aggressively. Report to 1 decimal place for percentages, 2 for per-100-word densities.
  • List concrete examples for every device you identify. Numbers without examples are useless.
  • If a metric reads zero, report it explicitly. Absence is data.

Phase 10: Save Prompt

After presenting the report, ask the user:

Style DNA report ready. Want me to save it as [source-filename]-style-dna.md next to the source file?

Wait for confirmation before writing. If the user says yes, save the full report. If analyzing multiple files, also offer to save the cross-article comparison as a separate file.


Integration

Produces Style DNA reports consumed by other skills:

[writing samples] --> style-forensics --> Style DNA report
                                              |
                                              +--> style-writer (write new content in that voice)
                                              +--> humanizer (preserve style when stripping AI tells)
                                              +--> copy-editor (respect voice during editing)
  • Before style-forensics: Gather 1-5 writing samples (pre-AI preferred)
  • After style-forensics: style-writer to write new content matching the voice
  • Not this skill: brand-voice for qualitative brand guidelines, copy-editor for grammar review

平台分布

Codex

36.14%
按下载量换算29

Claude

28.89%
按下载量换算23

Cursor

17.04%
按下载量换算13

Gemini CLI

8.78%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

执行命令

安装流程涉及命令执行,可能通过 npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill style-forensics 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills