context

Load service metadata, plans, and recent artifacts into a conversation.

Updated Apr 28, 2026

Search Tags:#service metadata #contextual information #service plans #recent artifacts #service understanding

Ready to run

npx skills add https://github.com/cfarvidson/sapling --skill context-cfarvidson

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: context
Source: https://github.com/cfarvidson/sapling/tree/main/packages/claude-plugin/skills/context
Command: npx skills add https://github.com/cfarvidson/sapling --skill context-cfarvidson

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill resolves the issue of agents not having access to the necessary context when working on a service, ensuring they can ground themselves and perform their tasks effectively.

Core Features & Use Cases

Contextual Information: Provides metadata, plans, and recent artifacts for a service.
Service-specific Details: Offers service name, repository, tech stack, dependencies, and conventions.
Planning & Artifacts: Lists plans and recent artifacts, including their IDs, statuses, and titles.
Use Case: Before an agent starts working on a service, they can use this Skill to get a comprehensive overview of the service's context, which helps in understanding the project's scope and making informed decisions.

Quick Start

To load the context for a service, use the command: /sapling:context <service>

Frequently Asked Questions about context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I load service metadata and recent artifacts into my agent conversation?▼

You can load service metadata, plans, and recent artifacts into your conversation by invoking the /sapling:context <service> command. This populates the context with service name, repository, tech stack, dependencies, and conventions for agent grounding.

What contextual information is needed before an agent starts working on a service?▼

Before working on a service, an agent needs contextual information including service metadata, repository details, tech stack, dependencies, conventions, and lists of recent plans and artifacts with their IDs and statuses.

Can I use this context loading approach without granting access to service plans and artifacts?▼

No, you cannot use this context loading approach without access. The skill explicitly requires access to service information and the ability to list plans and recent artifacts to successfully load the complete service context.

What's the best way to provide service understanding to an AI agent before starting development?▼

The best way to provide service understanding is to load complete context directly into the conversation. This gives the agent a comprehensive overview of the project scope, ensuring it can ground itself and make informed decisions.

Does this context loader require any external dependencies to list recent artifacts?▼

No external dependencies are required to list recent artifacts. The skill operates independently using its internal scripts and references to retrieve service metadata, plans, and artifact details.

Why does my agent lack project scope understanding when assigned to a new service?▼

Your agent lacks project scope understanding because it does not have access to necessary service context. Loading detailed metadata, plans, and recent artifacts resolves this issue by grounding the agent before task execution.