context-intelligence-session-navigation Skill
Use when extracting session data directly from JSONL files — the fallback when the graph server is unavailable or outside graph-analyst. Published by microsoft in amplifier-bundle-context-intelligence.
Decision snapshot
Is this a fit?
Data analysis, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is context-intelligence-session-navigation Skill?
Use when extracting session data directly from JSONL files — the fallback when the graph server is unavailable or outside graph-analyst. Published by microsoft in amplifier-bundle-context-intelligence. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Data analysis
- Data analysis use cases
Declared skill metadata
- Declared license: MIT
- Source file: skills/context-intelligence-session-navigation/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use context-intelligence-session-navigation Skill
- Use it for data analysis.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/amplifier-bundle-context-intelligence
- Skill file: skills/context-intelligence-session-navigation/SKILL.md
What it does
Use when extracting session data directly from JSONL files — the fallback when the graph server is unavailable or outside graph-analyst.
Skill instructions
Context Intelligence Session Navigation This skill covers navigation of flat JSONL session files written by the LoggingHandler. These files are the universal baseline — always present regardless of whether graph stores are configured. Use shell tools (jq, grep, wc, head) to extract data safely. For the complete event-by-event field reference, see context/event-schema.md. For ready-to-use jq/grep recipes, see context/safe-extraction-patterns.md. --- Disk Layout Resolve the root once before any discovery: bash CONTEXTINTELLIGENCEROOT="${AMPLIFIERCONTEXTINTELLIGENCEBASEPATH:-$HOME/.amplifier/projects}" $CONTEXTINTELLIGENCEROOT/{project-slug}/sessions/{sessionid}/context-intelligence/ ├── events.jsonl one JSON object per line, append-only └── metadata.json session metadata, written on start, updated on end - $CONTEXTINTELLIGENCEROOT — resolved from the idiom "${AMPLIFIERCONTEXTINTELLIGENCEBASEPATH:-$HOME/.amplifier/projects}" (unset → legacy default). Relocation is reader-visible ONLY via
Verified compatibility and discovery
Frequently asked questions
What is context-intelligence-session-navigation?
context-intelligence-session-navigation is a open-source AI agent skill with Copy skill directory. Use when extracting session data directly from JSONL files — the fallback when the graph server is unavailable or outside graph-analyst.
Who is context-intelligence-session-navigation best for?
context-intelligence-session-navigation is best for reusing agent instructions, scripts, and references, data analysis workflows.
How do I install context-intelligence-session-navigation?
Install or run context-intelligence-session-navigation using Copy skill directory. Check context-intelligence-session-navigation for the latest setup command.
Is context-intelligence-session-navigation actively maintained?
context-intelligence-session-navigation may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
