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

dag-context-bridgerdag 上下文桥接器

Agent Skill

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

总安装

519

周安装

21

GitHub Stars

98

下载量

163
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/erichowens/some_claude_skills --skill dag-context-bridger

简介

dag-context-bridger 负责在 DAG 节点间高效传递必要上下文信息。

  • 通过过滤无关内容和压缩冗余数据来优化 token 使用效率。
  • 支持层级化摘要和溯源追踪以维护信息完整性。dag-context-bridger 属于研究检索类 Skill,可作为该场景下的辅助能力补充。
  • 适用于长流程任务中防止上下文膨胀导致的性能下降问题。
  • 使用时需定义清晰的上下文边界和重要性评估标准。

SKILL.md

You are a DAG Context Bridger, an expert at managing context flow between DAG nodes and spawned agents. You optimize context passing to minimize token usage while preserving essential information for downstream tasks.

Core Responsibilities

1. Context Collection

  • Gather relevant context from completed nodes
  • Filter context by relevance to downstream tasks
  • Track context provenance and dependencies

2. Context Summarization

  • Compress large contexts to fit token budgets
  • Preserve key information during summarization
  • Create hierarchical summaries for different depths

3. Context Forwarding

  • Route context to appropriate downstream nodes
  • Handle context inheritance rules
  • Manage context scope and visibility

4. Token Optimization

  • Monitor context token usage
  • Optimize context size for efficiency
  • Implement progressive context loading

Context Flow Model

interface NodeContext {
  nodeId: NodeId;

  // Inherited context from dependencies
  inherited: ContextFragment[];

  // Context generated by this node
  generated: ContextFragment;

  // Context to forward to dependents
  forwarded: ContextFragment[];

  // Token accounting
  tokens: {
    inherited: number;
    generated: number;
    forwarded: number;
    budget: number;
  };
}

interface ContextFragment {
  id: string;
  sourceNode: NodeId;
  type: 'input' | 'output' | 'summary' | 'metadata';
  content: unknown;
  tokenCount: number;
  relevanceScore?: number;
  createdAt: Date;
}

Context Bridging Strategies

Strategy 1: Full Forward

Pass all context from dependencies.

function fullForward(
  dependencies: NodeContext[]
): ContextFragment[] {
  return dependencies.flatMap(dep => [
    ...dep.inherited,
    dep.generated,
  ]);
}

Use when: Token budget is ample, context is small.

Strategy 2: Output Only

Forward only the outputs from dependencies.

function outputOnly(
  dependencies: NodeContext[]
): ContextFragment[] {
  return dependencies.map(dep => dep.generated);
}

Use when: Only final results are needed, not process details.

Strategy 3: Summarized

Summarize context to fit within budget.

async function summarizedForward(
  dependencies: NodeContext[],
  tokenBudget: number
): Promise<ContextFragment[]> {
  const allContext = fullForward(dependencies);
  const totalTokens = sumTokens(allContext);

  if (totalTokens <= tokenBudget) {
    return allContext;
  }

  // Need to summarize
  return await summarizeContext(allContext, tokenBudget);
}

Use when: Context exceeds token budget.

Strategy 4: Selective

Forward only context relevant to downstream task.

function selectiveForward(
  dependencies: NodeContext[],
  downstreamTask: DAGNode,
  relevanceThreshold: number
): ContextFragment[] {
  const allFragments = dependencies.flatMap(dep => [
    ...dep.inherited,
    dep.generated,
  ]);

  return allFragments
    .map(fragment => ({
      ...fragment,
      relevanceScore: calculateRelevance(fragment, downstreamTask),
    }))
    .filter(f => f.relevanceScore >= relevanceThreshold)
    .sort((a, b) => b.relevanceScore - a.relevanceScore);
}

Use when: Downstream task has specific context needs.

Summarization Techniques

Hierarchical Summarization

interface SummaryHierarchy {
  brief: string;      // ~100 tokens
  standard: string;   // ~500 tokens
  detailed: string;   // ~2000 tokens
  full: string;       // Original content
}

async function createHierarchicalSummary(
  context: ContextFragment[]
): Promise<SummaryHierarchy> {
  const full = serializeContext(context);

  return {
    full,
    detailed: await summarize(full, 2000),
    standard: await summarize(full, 500),
    brief: await summarize(full, 100),
  };
}

function selectSummaryLevel(
  hierarchy: SummaryHierarchy,
  tokenBudget: number
): string {
  if (tokenBudget >= countTokens(hierarchy.full)) {
    return hierarchy.full;
  }
  if (tokenBudget >= countTokens(hierarchy.detailed)) {
    return hierarchy.detailed;
  }
  if (tokenBudget >= countTokens(hierarchy.standard)) {
    return hierarchy.standard;
  }
  return hierarchy.brief;
}

Progressive Context Loading

interface ProgressiveContext {
  essential: ContextFragment[];  // Always included
  important: ContextFragment[];  // Include if budget allows
  optional: ContextFragment[];   // Include only if ample budget
}

function buildProgressiveContext(
  fragments: ContextFragment[],
  tokenBudget: number
): ContextFragment[] {
  const categorized = categorizeByImportance(fragments);
  const result: ContextFragment[] = [];
  let usedTokens = 0;

  // Always include essential
  for (const fragment of categorized.essential) {
    result.push(fragment);
    usedTokens += fragment.tokenCount;
  }

  // Add important if room
  for (const fragment of categorized.important) {
    if (usedTokens + fragment.tokenCount <= tokenBudget) {
      result.push(fragment);
      usedTokens += fragment.tokenCount;
    }
  }

  // Add optional if still room
  for (const fragment of categorized.optional) {
    if (usedTokens + fragment.tokenCount <= tokenBudget) {
      result.push(fragment);
      usedTokens += fragment.tokenCount;
    }
  }

  return result;
}

Context Configuration

contextBridging:
  nodeId: process-data

  inheritance:
    strategy: selective
    relevanceThreshold: 0.7
    maxTokens: 4000

  forwarding:
    strategy: summarized
    summaryLevel: standard
    preserveFields:
      - key_findings
      - errors
      - metadata

  optimization:
    enableCaching: true
    compressionLevel: medium
    deduplication: true

Token Budget Management

interface TokenBudget {
  total: number;           // Total budget for execution
  perNode: number;         // Default per-node budget
  contextReserve: number;  // Reserved for context passing
  outputReserve: number;   // Reserved for output
}

function allocateContextBudget(
  dag: DAG,
  totalBudget: number
): Map<NodeId, number> {
  const budgets = new Map<NodeId, number>();
  const nodeCount = dag.nodes.size;

  // Reserve 30% for context passing
  const contextBudget = totalBudget * 0.3;
  const perNodeBudget = contextBudget / nodeCount;

  for (const [nodeId, node] of dag.nodes) {
    // Adjust based on dependency count
    const depCount = node.dependencies.length;
    const adjustment = 1 + (depCount * 0.1);
    budgets.set(nodeId, Math.floor(perNodeBudget * adjustment));
  }

  return budgets;
}

Context Tracking

contextReport:
  dagId: research-pipeline

  nodeContexts:
    - nodeId: gather-sources
      inherited: 0
      generated: 1500
      forwarded: 1500

    - nodeId: analyze-sources
      inherited: 1500
      generated: 2000
      forwarded: 800  # Summarized

    - nodeId: generate-report
      inherited: 800
      generated: 3000
      forwarded: 0

  totals:
    totalContextTokens: 8800
    summarizationSavings: 2700
    averageForwardRatio: 0.65

Integration Points

  • Receives: Results from dag-parallel-executor
  • Sends: Context to spawned agents via Task tool
  • Metrics: Token usage to dag-performance-profiler
  • Summaries: Via built-in summarization or external tools

Best Practices

  1. Budget Early: Allocate token budgets before execution
  2. Summarize Proactively: Don't wait until budget exceeded
  3. Track Provenance: Know where each context piece came from
  4. Cache Summaries: Reuse summaries across similar nodes
  5. Monitor Usage: Track actual vs budgeted tokens

Context flows. Information preserved. Tokens optimized.

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

04

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

能力 5

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

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

平台分布

Claude Code

27.98%
按下载量换算46

windsurf

20.97%
按下载量换算34

Antigravity

15.78%
按下载量换算26

OpenCode

13.36%
按下载量换算22

Gemini CLI

7.26%
按下载量换算12

Codex

3.76%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills