Token导航 LogoToken导航TokenDH.com
研究检索权限需确认github未标认证来源可访问clear审计通过

loglinelogline 搜索

Agent Skill

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

总安装

306

周安装

13

GitHub Stars

28

下载量

107
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/bybren-llc/story-systems-template --skill logline

简介

logline 用于查找、检索和筛选相关信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词、任务场景或来源线索快速定位候选结果。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装并使用。
  • 安装前需确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写操作。
  • logline 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Logline Skill

Invocation Triggers

Apply this skill when:

  • Distilling a story to its essential hook
  • Preparing pitch materials
  • Testing if a concept is clear and compelling
  • Marketing a screenplay

What is a Logline?

A logline (also called a "hook") is a one to two sentence description of your movie that captures the essence of the story in a way that makes people want to see it.

The Four Components of a Hook

Per WTFB methodology, every effective hook contains these four elements:

1. Characters

  • Who are they?
  • What do they want?
  • What are their goals?

2. Conflict

  • What is the main obstacle to achieving their goal?
  • Who or what opposes them?

3. Setting

  • Time period
  • Genre
  • Style/tone

4. Action

  • What exciting things happen?
  • Never be boring!

Logline Formula

[ADJECTIVE] [PROTAGONIST TYPE] must [GOAL/ACTION]
when [INCITING INCIDENT/CONFLICT],
or else [STAKES].

Alternative Formula

When [SETUP], a [PROTAGONIST] must [OBJECTIVE]
before [ANTAGONIST] [THREAT].

Genre-Specific Formula

A [GENRE] about [PROTAGONIST] who [SITUATION]
until [CATALYST] forces them to [ACTION]
against [ANTAGONIST/OBSTACLE].

Classic Logline Examples

Raiders of the Lost Ark

"An archeologist is hired by the U.S. government to find the Ark of the Covenant before the Nazis."

Breakdown:

  • Character: Archeologist (implies adventure, intelligence)
  • Conflict: Race against Nazis
  • Setting: Implied WWII era, adventure genre
  • Action: "Find" + competing with Nazis = excitement

Gladiator

"A Roman general is betrayed and his family killed by an insane emperor. Now a gladiator, he comes to Rome for revenge."

Breakdown:

  • Character: Roman general (status, skill)
  • Conflict: Betrayal, loss, revenge against emperor
  • Setting: Roman era, epic drama
  • Action: Gladiator combat, revenge journey

Logline Development Worksheet

Step 1: Core Elements

PROTAGONIST: ___________________________________
(Be specific: not "a man" but "a disgraced surgeon")

GOAL: ___________________________________
(What do they actively pursue?)

ANTAGONIST/OBSTACLE: ___________________________________
(Person, force, or circumstance opposing them)

STAKES: ___________________________________
(What happens if they fail?)

UNIQUE ELEMENT: ___________________________________
(What makes THIS story different?)

Step 2: Draft Loglines

Draft 1 (Basic):

___________________________________________________
___________________________________________________

Draft 2 (Add specificity):

___________________________________________________
___________________________________________________

Draft 3 (Add stakes):

___________________________________________________
___________________________________________________

Final Logline:

___________________________________________________
___________________________________________________

Logline Quality Checklist

Must Have

  • Protagonist clearly identified
  • Goal/objective stated
  • Conflict/obstacle present
  • Implies genre
  • One to two sentences maximum
  • Creates desire to know more

Should Have

  • Unique hook or twist
  • Stakes implied or stated
  • Active voice (character DOES something)
  • Specific rather than vague

Must Avoid

  • No questions ("What if...?")
  • No character names (unless famous)
  • No theme statements
  • No backstory
  • No "and then" chains

Common Logline Mistakes

MistakeExampleFix
Too vague"A man faces challenges""A retired hitman hunts the men who killed his dog"
Too longMultiple sentencesCut to one powerful sentence
No conflict"A woman discovers her past""A woman must confront the cult that raised her"
Passive"A story about love""A dying man races to reconnect with his estranged daughter"
Lists events"First X, then Y, then Z"Focus on central conflict
Theme not story"An exploration of grief""A widow must solve her husband's murder"

Genre-Specific Tips

Action/Thriller

  • Emphasize physical stakes and ticking clock
  • "Must stop X before Y happens"

Comedy

  • Hint at the comedic situation or irony
  • Include the fish-out-of-water element

Drama

  • Focus on internal conflict made external
  • Emphasize emotional stakes

Horror

  • Establish the threat
  • Imply isolation or helplessness

Romance

  • Show the obstacle to love
  • Include what makes this couple unique

Logline Testing

Share your logline and ask:

  1. Do they understand the genre?
  2. Do they know who the protagonist is?
  3. Can they identify the conflict?
  4. Do they want to know what happens?
  5. Can they picture the movie?

If "no" to any, revise.

Validation Checklist

  • Logline is 25 words or fewer
  • Protagonist is specific and interesting
  • Goal is clear and active
  • Conflict/obstacle is compelling
  • Stakes are implied or stated
  • Genre is clear
  • Creates curiosity to see the film
  • No character names used
  • Active voice throughout

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Cursor

30.13%
按下载量换算32

Claude Code

25.46%
按下载量换算27

openhands

16.86%
按下载量换算18

kilo

12.74%
按下载量换算14

windsurf

8.2%
按下载量换算9

zencoder

3.71%
按下载量换算4

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

权限需确认

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

来源信息

继续浏览同类 Skills