Token导航 LogoToken导航

Agent Skill · 待分类

giggle-generation-scripts(咯咯笑生成脚本)

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

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

总安装 1,247周安装 53GitHub Stars 公开资料未说明下载 437核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/giggle-official/skills --skill giggle-generation-scripts

这个 Skill 是做什么的

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

giggle-generation-scripts 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在开发协作中整理相关事项。适用于围绕仓库状态、代码变更或协作事项进行信息整理和分析的场景。通过 npx skills add 命令从指定 GitHub 仓库安装使用。

安装前需确认权限范围、维护状态,注意是否触发联网或文件操作。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/giggle-generation-scripts

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

giggle-generation-scripts 怎么安装?

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

giggle-generation-scripts 支持哪些 AI 工具?

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

giggle-generation-scripts 需要什么权限?

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

giggle-generation-scripts 是免费的吗?

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

giggle-generation-scripts 用的人多吗?

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

giggle-generation-scripts 安全吗?

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

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

值得选的地方

  • 同时适配 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操作浏览器未明确未通过
giggle-generation-scripts

咯咯笑生成脚本 · 本页

1,247—只读未明确通过

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

SKILL.md 原文

Giggle Generation Scripts

Organizes text with "high-density conflict + black humor + subtext-heavy dialogue + narrative reversals". Does not copy specific film scenes or lines.

No Retry on Error: If script execution encounters an error, do not retry. Report the error to the user directly and stop.

Input Collection

Prioritize collecting:

  • Genre and era: Republican China, contemporary, near-future, etc.
  • Core conflict: power, money, identity, revenge, misunderstanding
  • Protagonist goal: what they want, what they fear losing
  • Character relations: allies, opponents, double-dealers
  • Target length: short film, single episode, feature

If missing, fill in and state assumptions explicitly.

Input Conflict Handling

Check for conflicting user inputs first. If conflicts exist, handle in this order:

  1. Tone conflicts (e.g. "light comedy" + "extremely dark tragedy")
  2. Character conflicts (e.g. "pure good" + "actively evil protagonist")
  3. Length conflicts (e.g. "5-minute short" + "20 full scenes")

Rules:

  • Prefer the user's latest constraint; if still inconsistent, offer 2 alternative directions, then continue.
  • When info is missing, add at most 3 key assumptions and list them in a "Assumptions" section before the body.
  • Do not treat unconfirmed settings as given facts.

Output Mode Selection

Choose mode by user goal and context length. Default: "standard".

  • Quick: Synopsis + character bios (for direction-setting)
  • Standard: Synopsis + character bios + scene outline + at least 3 full scene scripts
  • Long: Synopsis + character bios + scene outline + 6–10 full scene scripts

Output Order

Output strictly in this order:

  1. Synopsis (300–600 characters)
  2. Character bios (3–8 people; each: surface identity / true motive / relational tension / speech style)
  3. Scene outline (8–20 scenes; each: scene-location-time-conflict core-turning point)
  4. Scene scripts (at least 3 full examples)

Scene Script Serial Output Protocol

When outputting scene scripts, use serial interaction. Do not send all at once:

  1. Always start from scene 1 (S01).
  2. Output only one complete scene at a time (dialogue, action, staging, hook).
  3. At the end of each scene, always ask: "Continue to next scene (S0X)?"
  4. Output the next scene only after explicit user confirmation.
  5. If the user requests "output all at once", switch to batch mode after confirming first.

Scene Script Format

Use a uniform template per scene:

【Scene】S03
【Location/Time】County office courtyard / night
【Characters】Ma Zouri, Huang Silang, Accountant
【Scene goal】Ma Zouri wants to extract where the silver notes went; Huang Silang wants to counter-scheme.
【Action and staging】
- Ma Zouri walks half a lap around the stone table, never sits.
- Huang Silang stands backlit; accountant slightly behind the two.
- Distant firecrackers interrupt when "rules" is mentioned.
【Dialogue】
Ma Zouri: This yard's wind cuts like a knife across the face.
Huang Silang: Wind not sharp, people can't stand.
Accountant: Gentlemen, the tea is getting cold.
Ma Zouri: Tea can warm; ledgers can't—that's when blood flows.
【Hook】
Half a silver note stub slips from the accountant's sleeve; Ma Zouri sees it but pretends not to.

Style Rules

Dialogue Technique (must follow)

  • Characters never answer directly; use rhetorical questions, analogy, topic shifts
  • Discuss life-and-death matters in everyday tone ("tea's cold" = "you're dead")
  • Each exchange is a power contest: answering = blocking, deflecting = dodging, counter-question = strike
  • In three-person scenes, the third character's lines pace the conflict
  • Forbidden: characters stating emotions directly ("I'm angry", "I'm scared")
  • Forbidden: explanatory dialogue ("You know, back then that thing was...")
  • Forbidden: characters summarizing for the audience ("So you mean...")

Single-Scene Rhythm Formula

Each scene advances in 4 beats:

  1. 【Probe】Both sides feel each other out with idle talk (1–2 rounds)
  2. 【Probe deeper】One side suddenly hits the real topic (1 round)
  3. 【Reversal】The probed side turns it around; power flips (2–3 rounds)
  4. 【Cliffhanger】Third party or accident interrupts; leave a hook

Every scene must have at least one relational shift: probe→threat, ally→suspicion, or power reversal.

Black Humor Technique

  • Core: serious situation + oddly calm/ordinary phrasing
  • Characters worry about trivial things when in grave danger (discussing tea varieties with a knife at the throat)
  • Discuss lives in business tone ("Thirty-six lives, wholesale or retail?")
  • Absurdity comes from logically consistent nonsense—each line alone sounds "reasonable", together it's absurd
  • Forbidden: internet memes, puns, slapstick (not Stephen Chow; Jiang Wen style)

Language Fingerprint Rule

  • Each character's speech pattern must be recognizable in every line
  • Cover character names; the lines alone should identify who speaks
  • After writing: randomly pick 3 lines—can you tell who said them by tone? If not, rewrite.

Interruption Rhythm

  • Dialogue must be "dense"—responses within a breath, like ping-pong
  • Two-person: back-and-forth without pause; three-person: like passing a ball, third can interrupt anytime
  • Allow interruption; mark cut-off lines with "—"
  • At least one interruption per scene (B starts before A finishes)
  • Short lines (roughly 5–15 words or one breath) mainly; occasional long line to reset rhythm
  • Forbidden: each person delivers a long monologue in turn (that's speechifying, not dialogue)

Information Density (two layers per scene)

  • Each scene's dialogue carries at least two layers: surface topic + real topic
  • If a scene advances only one thing, density is low—add a second layer
  • Add by: dialogue says A, action/props reveal B; or dialogue literally discusses A while subtext is B
  • Self-check: remove all action cues; can the audience feel "they're not just talking about this" from dialogue alone? If not, rewrite.
  • Reference: 10 lines per scene should advance at least 2 info points + 1 relationship change

Word Precision

  • After each line: can you cut one word? Cut it.
  • Can you replace with a more precise word? Small wording shifts change identity and attitude (e.g. formal vs familiar address; walk vs get lost).
  • Lines should "taste" when spoken: use punchy words, avoid formal and cliché phrases
  • Prefer verbs: specific action over abstract description ("He slaps chopsticks on the table" beats "He's angry")
  • Forbidden: purple prose, broadcaster / announcer tone, trendy internet slang that breaks period voice

Other Style Requirements

  • Every 2–3 scenes: one info reversal; prefer action over narration
  • Action and staging serve story: position, gaze, noise, props must drive conflict

Quality Checklist

Before output, verify:

  • All four parts present and in order
  • Character motives interlock, not isolated
  • Each scene has a goal and a change
  • Dialogue is speakable and distinguishes voices
  • No direct copy of existing film scenes or lines
  • Each scene follows 4-beat rhythm (probe→deeper→reversal→hook)
  • Black humor present (everyday tone for dangerous matters)
  • Can you distinguish characters by tone with names hidden?
  • No forbidden items (direct emotion, explanatory dialogue, summarizing for audience)
  • Dialogue dense enough; interruptions present (not turn-taking)
  • Two layers of information per scene (surface + real)
  • Lines trimmed; deleted what can be deleted; words concrete and strong

Revision Loop

When iterating, do at most 2 focused revision rounds; each round only one dimension:

  • Conflict intensity (more restrained / sharper)
  • Dialogue tone (more subtle / more pointed)
  • Staging (more static / more dynamic)

Each round: first output "this round's changes (up to 3)", then the revised excerpts, not a full rewrite.

Example Reference

To adapt quickly, read references/examples.md and replace setting/characters per the user's topic.

平台分布

Codex

34.38%
按下载量换算150

Claude

29.94%
按下载量换算131

Cursor

19.23%
按下载量换算84

Gemini CLI

8.88%
按下载量换算39

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills