Token导航 LogoToken导航

Agent Skill · 研究检索

session-context-injector(会话上下文注入器)

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

session-context-injector 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 32,329。

总安装 2,542周安装 107GitHub Stars 公开资料未说明下载 890核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:session-context-injector(会话上下文注入器)
来源仓库:https://github.com/nissan/session-context-injector
安装命令:
openclaw skills install session-context-injector
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install session-context-injector

这个 Skill 是做什么的

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

会话上下文注入器用于重置后重新定向 Telegram 聊天内容。适合读取 STATUS.md 文件并注入项目特定恢复点与下一步指引。可帮助重建中断的工作流,提升代理间交接效率。需注意 STATUS.md 文件是否存在,否则可能影响注入准确性。

session-context-injector 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install session-context-injector;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

session-context-injector 怎么安装?

在终端执行 openclaw skills install session-context-injector。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

session-context-injector 支持哪些 AI 工具?

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

session-context-injector 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

session-context-injector 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

session-context-injector 用的人多吗?

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

session-context-injector 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

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

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。

先想清楚的地方

  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

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

不太适合

  • 需要厂商级技术支持和 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调用外部服务未明确有提醒
session-context-injector

会话上下文注入器 · 本页

2,542—需要联网MIT-0有提醒

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

SKILL.md 原文

name
session-context-injector
version
1.0.0
description
Reorient a Telegram chat after a session reset. Reads a project's STATUS.md (resume point, blockers, next action) and sends a project-specific context injection message via the Telegram bot API. Use when: clearing session transcripts, creating new project rooms, or onboarding collaborators into a scoped chat. Supports 3 message variants: group refresh, direct DM summary, and new-room welcome.
metadata
openclaw
emoji
🔄
requires
bins
["python3"]
env
["TELEGRAM_BOT_TOKEN"]
network
outbound
true
reason
Sends messages to the Telegram Bot API (api.telegram.org) to inject context into group chats and DMs after session resets.
primaryEnv
TELEGRAM_BOT_TOKEN
tags

SKILL: session-context-injector

Use when: A Telegram chat session has been cleared, a collaborator joins a project room, a new project room is created, or any context needs to be re-anchored in a specific chat after a reset.

Why this exists: After a session clear, the next person to message gets a blank-slate AI with no project awareness. This skill ensures every reset is followed by a project-specific reorientation message — so the first reply in a fresh session is always oriented, not confused.

Invoked by:

  • playbooks/session-refresh/PLAYBOOK.md — Phase 3, after each session clear
  • playbooks/new-project/PLAYBOOK.md — Stage 5b, after room creation
  • playbooks/telegram-collaborator-room/PLAYBOOK.md — on collaborator join

Inputs

InputSourceRequired
chat_idsessions.json or telegram-groups.json✅
slugmemory/telegram-groups.json[chat_id].slug✅ for project rooms
project_namememory/telegram-groups.json[chat_id].name✅
bot_tokenop read "op://OpenClaw/Telegram Bot Token/credential"✅
STATUS.mdprojects/<slug>/STATUS.mdOptional — enriches message
chat_typegroup / direct / tui✅

Step 1 — Parse STATUS.md

If projects/<slug>/STATUS.md exists, extract:

import re

def parse_status(slug: str) -> dict:
    path = PROJECTS_DIR / slug / "STATUS.md"
    if not path.exists():
        return {}
    text = path.read_text()

    def extract(heading: str) -> str:
        m = re.search(
            rf"##+ {re.escape(heading)}\s*\
(.*?)(?=\
##|\Z)",
            text, re.DOTALL
        )
        return m.group(1).strip()[:400] if m else ""

    resume   = extract("RESUME FROM HERE") or extract("Resume From Here") or ""
    blockers = extract("Blockers") or extract("Open Blockers") or ""

    # Strip markdown bullets
    resume   = re.sub(r"^[-*] ", "", resume, flags=re.MULTILINE).strip()
    blockers = re.sub(r"^[-*] ", "", blockers, flags=re.MULTILINE).strip()

    return {
        "resume":   resume[:300],
        "blockers": blockers[:200],
    }

Fallback: If STATUS.md is missing or empty, use the generic template (Step 2b).


Step 2a — Build Project Room Message (group chat)

def build_group_message(project_name: str, slug: str, status: dict) -> str:
    resume   = status.get("resume", "")
    blockers = status.get("blockers", "")

    lines = [
        f"🔄 <b>Session Refresh — {project_name}</b>",
        "",
        "I've refreshed my context. Here's where we are:",
        "",
    ]

    if slug:
        lines.append(f"📌 <b>Project:</b> {slug.upper()}")
    if resume:
        lines.append(f"📍 <b>Resume from:</b> {resume}")
    if blockers and blockers.lower() not in ("none", "—", "-", ""):
        lines.append(f"🚧 <b>Blockers:</b> {blockers}")

    lines += [
        "",
        "My memory and project files are fully updated. "
        "Jump back in whenever you're ready — just pick up the thread. 🐾",
    ]
    return "\
".join(lines)

Character limit: Keep under 4096 chars (Telegram max). Truncate resume and blockers at the values above if STATUS.md is long.


Step 2b — Build Direct Chat Message (Nissan DM)

Use when chat_type == "direct" and the chat_id is Nissan's (821071206).

def build_direct_message(touched_projects: list[dict]) -> str:
    lines = [
        "🔄 <b>Daily Session Refresh</b>",
        "",
        "Context cleared. Memory and STATUS files are up to date.",
    ]
    if touched_projects:
        lines.append("")
        lines.append("Active projects refreshed:")
        for p in touched_projects[:10]:
            lines.append(f"• <b>{p['slug'].upper()}</b> — {p['name']}")
    lines += ["", "Anything you want to jump straight into? 🐾"]
    return "\
".join(lines)

Step 2c — Build New Room / Collaborator Join Message

Use when a room is freshly created or a collaborator joins for the first time (not a reset).

def build_welcome_message(project_name: str, slug: str, purpose: str, allowed_topics: list[str]) -> str:
    topic_list = "\
".join(f"• {t}" for t in allowed_topics[:8])
    return (
        f"👋 <b>Welcome to {project_name}</b>\
\
"
        f"{purpose}\
\
"
        f"<b>What I can help with here:</b>\
{topic_list}\
\
"
        f"I have full project context loaded. Ask me anything within scope. 🐾"
    )

Step 3 — Send via Telegram Bot API

import urllib.request, json

def send_injection(bot_token: str, chat_id: str, text: str, dry_run: bool = False) -> bool:
    if dry_run:
        print(f"[DRY-RUN] → {chat_id}: {text[:100].replace(chr(10),' ')}…")
        return True
    try:
        url     = f"https://api.telegram.org/bot{bot_token}/sendMessage"
        payload = json.dumps({
            "chat_id":    chat_id,
            "text":       text,
            "parse_mode": "HTML",
        }).encode()
        req = urllib.request.Request(
            url, data=payload,
            headers={"Content-Type": "application/json"}
        )
        with urllib.request.urlopen(req, timeout=10) as r:
            return r.status == 200
    except Exception as e:
        print(f"⚠️  Injection failed ({chat_id}): {e}")
        return False

Parse mode: Always use HTML (not Markdown). Markdown requires escaping; HTML is more predictable with <b> and <i>.

On failure: Log the failure, continue with other chats. Never block the refresh loop on a single failed send.


Step 4 — Log the Injection

After each successful send, append to memory/YYYY-MM-DD.md:

### Context Injection Sent — [project_name] — YYYY-MM-DD HH:MM AEST
- **Chat ID:** [chat_id]
- **Slug:** [slug]
- **Type:** [session-refresh / room-creation / collaborator-join]
- **Status:** ✅ sent / ❌ failed

And if the project has a STATUS.md, append a one-liner:

_Context injection sent: YYYY-MM-DD HH:MM AEST — session cleared._

Decision Rules

ConditionAction
STATUS.md exists + has contentUse Step 2a with extracted resume/blockers
STATUS.md missing or emptyUse Step 2a with slug + name only (no resume/blockers section)
chat_type == "direct" + NissanUse Step 2b
New room / first joinUse Step 2c
chat_id is NoneSkip Telegram send; log to memory only
bot_token unavailableLog failure to memory; do not crash
Message > 4096 charsTruncate resume to 200 chars, blockers to 100 chars

Example Output (group chat, STATUS.md found)

🔄 Session Refresh — OpenClaw — Portkey Gateway Integration

I've refreshed my context. Here's where we are:

📌 Project: PORTKEY
📍 Resume from: Test latency comparison between direct Anthropic calls and Portkey-routed calls. Script is at scripts/portkey-bench.py — needs --compare flag wired up.
🚧 Blockers: Portkey dashboard shows incorrect token counts for cache_read events — filed upstream.

My memory and project files are fully updated. Jump back in whenever you're ready — just pick up the thread. 🐾

Reuse Checklist

Before calling this skill from a playbook or script:

  • [ ] chat_id is confirmed (from sessions.json or telegram-groups.json)
  • [ ] bot_token retrieved from 1Password (not hardcoded)
  • [ ] slug verified — projects/<slug>/STATUS.md exists or graceful fallback confirmed
  • [ ] parse_mode: "HTML" — not Markdown
  • [ ] Failure is logged, not raised

ClawHub Tags

telegram, context-injection, session-refresh, project-rooms, reorientation


Changelog

  • 2026-04-03: Extracted from playbooks/session-refresh/PLAYBOOK.md Phase 3. Added welcome/join variant (Step 2c). Formalised as standalone reusable skill.

平台分布

OpenClaw

76.04%
按下载量换算677

安全审计

VirusTotal

可疑

ClawScan

可疑

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

继续浏览同类 Skills