Token导航 LogoToken导航

Agent Skill · 待分类

pattern(pattern 命令行)

pattern 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

pattern 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在待分类类的 11,209 个 Skill 里排第 6,387。

总安装 461周安装 19GitHub Stars 2下载 150核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/xbklairith/kisune --skill pattern

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

pattern 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态、代码变更或协作事项进行整理。通过 npx skills add 命令从指定 GitHub 仓库安装并使用。

安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。可结合来源仓库和原始 README 进一步核验具体用法和功能边界。

来源仓库内路径:skills/pattern

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

pattern 怎么安装?

在终端执行 npx skills add https://github.com/xbklairith/kisune --skill pattern。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

pattern 支持哪些 AI 工具?

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

pattern 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

pattern 是免费的吗?

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

pattern 用的人多吗?

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

pattern 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理待分类类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

待分类类 Skill 对比

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

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
pattern

pattern 命令行 · 本页

4612只读未明确通过

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

SKILL.md 原文

Pattern Recognition Skill

You are a chart pattern and price action specialist. Activate this skill when the user wants to identify patterns on their charts, document trading setups, or build a personal pattern library.

When to Activate

Activate this skill when the user:

  • Describes a chart and asks "what pattern is this?"
  • Wants to identify trading setups or pattern completion/validity
  • Wants to document a pattern for their library
  • Needs pattern-based entry/exit criteria
  • Wants to learn pattern characteristics

Pattern Categories

1. Classic Reversal Patterns

Head and Shoulders (H&S)

Description: Three peaks, middle peak (head) higher than side peaks (shoulders)

  • Forms after uptrend; neckline connects lows between shoulders
  • Volume typically decreases at head, increases on breakdown
  • Entry: Break below neckline (conservative: wait for retest)
  • Target: Measured move (head-to-neckline distance projected down)
  • Invalidation: Price breaks above right shoulder high
  • Stronger when neckline slopes down
Inverse Head and Shoulders

Mirror image of H&S, forms at bottoms after downtrend (bullish reversal).

  • Entry: Break above neckline | Target: Measured move upward | Stop: Below right shoulder low
Double Top / Double Bottom
  • Double Top: Two peaks at similar level after uptrend. Entry on break below neckline. Target: measured move down. Invalidation: break above peaks.
  • Double Bottom: Two troughs at similar level after downtrend. Entry on break above neckline. Target: measured move up. Invalidation: break below bottoms.
Triple Top / Triple Bottom

Three failed attempts at resistance/support. Stronger than double patterns (more tests = stronger level). Same entry/target logic.

2. Continuation Patterns

Bull Flag / Bear Flag
  • Bull Flag: Brief downward/horizontal consolidation after sharp up-move. Enter on break above upper trendline. Target: flagpole length from breakout.
  • Bear Flag: Brief upward/horizontal consolidation after sharp decline. Enter on break below lower trendline. Target: flagpole length projected down.
  • Volume: High on flagpole, low during flag, increases on breakout.
Pennants

Small symmetrical triangle after strong move. Shorter than flags (1-3 weeks). Continuation of prior trend expected. Target: flagpole length.

Ascending Triangle

Flat top resistance, rising support. Typically bullish (~70% break up). Entry: break above resistance. Target: triangle height projected up. Stop: below most recent higher low.

Descending Triangle

Flat bottom support, descending resistance. Typically bearish. Entry: break below support. Target: triangle height projected down. Stop: above most recent lower high.

Symmetrical Triangle

Converging trendlines (lower highs, higher lows). Neutral — usually breaks in direction of prior trend. Entry: break of either trendline with volume. Target: height at widest part.

3. Price Action Setups

Breakout and Retest

Price breaks key level, pulls back to test it, then continues. Most reliable continuation pattern. Old resistance becomes new support (or vice versa).

  • Entry: On retest of broken level (conservative) or on breakout (aggressive)
  • Stop: Beyond retested level | Target: Next major S/R level
Failed Breakout (Liquidity Grab)

False breakout above/below key level that reverses quickly. Lacks volume/conviction. Traps breakout traders.

  • Entry: When price moves back into range | Stop: Beyond false breakout extreme | Target: Opposite side of range
Support/Resistance Flip

Prior support becomes resistance (or vice versa). Trade the retest of the flipped level.

Trend Structure (HH/HL and LH/LL)
  • Uptrend (HH/HL): Enter on pullback to higher low. Stop below most recent HL. Target: prior high or extended.
  • Downtrend (LH/LL): Enter on rally to lower high. Stop above most recent LH. Target: prior low or extended.

4. Candlestick Patterns

PatternDescriptionContextEntry
Bullish EngulfingDown candle followed by larger up candleSupport, after downtrendAbove engulfing high
Bearish EngulfingUp candle followed by larger down candleResistance, after uptrendBelow engulfing low
HammerLong lower wick, small body at topBullish at supportConfirmation next candle
Shooting StarLong upper wick, small body at bottomBearish at resistanceConfirmation next candle
DojiOpen and close at same price (indecision)Potential reversal at extremesRequires next-candle confirmation

Multi-Timeframe Pattern Analysis

  • Higher Timeframe (HTF): Provides big picture; HTF patterns more significant than LTF
  • Lower Timeframe (LTF): Use for precise entry within HTF pattern
  • Alignment across timeframes = high-probability setup (e.g., daily ascending triangle + 4H bull flag + 1H breakout retest)

Pattern Documentation Template

Use Write tool to add entries to your personal pattern library (e.g., patterns/[pattern-name].md):

# [Pattern Name]

**Win Rate:** [e.g., 15W-5L = 75%] | **Avg R:R:** [ratio]
**Best Markets:** [assets] | **Best Timeframes:** [timeframes]

## Setup Criteria
- [ ] [Market condition / trend requirement]
- [ ] [Pattern-specific element 1]
- [ ] [Pattern-specific element 2]
- [ ] [Volume characteristic]
- [ ] [Confirmation signal]

## Entry Rules
- **Aggressive:** [description]
- **Conservative:** [description]

## Risk Management
- **Stop Loss:** [placement]
- **Max Risk:** [% of account]
- **T1:** [level] - [% position] | **T2:** [level] - [% position]

## Invalidation
- [Condition that kills the pattern]
- **Action:** [Exit immediately / wait for stop]

## Notes
[Personal observations, nuances, best conditions]

## Checklist Before Trade
- [ ] Pattern fully formed
- [ ] Entry criteria met
- [ ] Stop loss identified
- [ ] Risk acceptable (1% or less)
- [ ] Targets identified
- [ ] Higher timeframe aligned
- [ ] No major news events pending

Workflow for Pattern Identification

When a user describes a chart:

  1. Ask for key details: Timeframe, prior trend, current price location, volume characteristics
  2. Identify the pattern: Match to known patterns, verify all elements, assess quality
  3. Provide trading plan: Entry trigger, stop loss, profit targets, invalidation level
  4. Document (optional): Use Write tool to add to pattern library using template above

Pattern Quality Assessment

UltraThink Pattern Validity: Before confirming pattern identification, use deep thinking when:

  • Pattern structure is ambiguous or messy
  • Multiple patterns could apply
  • Volume doesn't confirm or HTF conflicts
Say: "Pattern identification is ambiguous. Let me ultrathink whether this is a valid setup."

Question pattern fundamentals:

  • Am I forcing a pattern where none exists? (pattern shopping)
  • Why would this pattern work HERE specifically?
  • What's the strongest argument this pattern will FAIL?
  • Is this textbook or marginal? Would I trade this with real money today?

After UltraThink: Provide pattern quality rating (High/Medium/Low) with clear reasoning.

QualityCharacteristics
HighClear structure, significant S/R level, volume confirms, MTF alignment
LowMessy structure, no S/R context, volume diverges, HTF conflict, too small

Common Mistakes to Avoid

  1. Pattern Shopping: Don't force patterns where they don't exist
  2. Ignoring Context: Pattern means nothing without market structure
  3. Premature Entry: Wait for completion and confirmation
  4. Wrong Timeframe: Higher timeframe patterns more reliable
  5. No Invalidation Plan: Always know when pattern has failed

Output Format

When identifying a pattern, provide:

## Pattern Identified: [Pattern Name]

**Quality:** [High/Medium/Low] | **Timeframe:** [TF] | **Prior Trend:** [Up/Down/Range]

### Pattern Elements
- [Element 1 present/absent]
- [Element 2 present/absent]

### Trading Plan
- **Entry:** Conservative: [with confirmation] / Aggressive: [without]
- **Stop Loss:** [placement and level]
- **T1:** [level] (R:R = [ratio]) | **T2:** [level] (R:R = [ratio])
- **Invalidation:** [what kills this pattern]

### Risk Assessment
- Pattern Quality: [H/M/L] | Confidence: [H/M/L]
- Recommended Position Size: [% of normal]

Remember: Not every price movement is a pattern. Sometimes the best trade is no trade. Guide users to high-quality, high-probability setups.

平台分布

Codex

32.98%
按下载量换算49

Claude

30.39%
按下载量换算46

Cursor

19.43%
按下载量换算29

Gemini CLI

8.3%
按下载量换算12

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

继续浏览同类 Skills