Agent skill

Search Context

Find, clone, inspect, and summarize high-quality GitHub reference repositories for coding agents.

MITAuto-check passedMobile

Install Search Context

skills CLI

$ npx skills add instructa/agent-skills --skill search-context -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install instructa/agent-skills search-context --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/instructa/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/engineering/search-context .claude/skills/search-context && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "search-context" agent skill from https://github.com/instructa/agent-skills/tree/main/skills/engineering/search-context into .claude/skills/search-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search-context", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/instructa/agent-skills/tree/main/skills/engineering/search-context

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add instructa/agent-skills --skill search-context -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install instructa/agent-skills search-context --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/instructa/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/engineering/search-context .agents/skills/search-context && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "search-context" agent skill from https://github.com/instructa/agent-skills/tree/main/skills/engineering/search-context into .agents/skills/search-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search-context", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add instructa/agent-skills --skill search-context -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install instructa/agent-skills search-context --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/instructa/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/engineering/search-context .cursor/skills/search-context && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "search-context" agent skill from https://github.com/instructa/agent-skills/tree/main/skills/engineering/search-context into .cursor/skills/search-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search-context", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/instructa/agent-skills.git --path skills/engineering/search-context

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add instructa/agent-skills --skill search-context -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install instructa/agent-skills search-context --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/instructa/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/engineering/search-context .gemini/skills/search-context && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "search-context" agent skill from https://github.com/instructa/agent-skills/tree/main/skills/engineering/search-context into .gemini/skills/search-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search-context", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install instructa/agent-skills search-context

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add instructa/agent-skills --skill search-context -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/instructa/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/engineering/search-context .github/skills/search-context && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "search-context" agent skill from https://github.com/instructa/agent-skills/tree/main/skills/engineering/search-context into .github/skills/search-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search-context", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add instructa/agent-skills --skill search-context -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install instructa/agent-skills search-context --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/instructa/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/engineering/search-context .opencode/skills/search-context && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "search-context" agent skill from https://github.com/instructa/agent-skills/tree/main/skills/engineering/search-context into .opencode/skills/search-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search-context", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: search-context
GitHub stars: 139
Token cost: ~2.1k tokens
SKILL.md length: 967 words
Files: 17 (incl. scripts, references)
Skills in repo: 17
Repo updated: Sep 28, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Find, clone, inspect, and summarize high-quality GitHub reference repositories for coding agents.

Works in 9 steps: Convert the user request into concise… → If the user asks for local/third-party… → Use GitHub repository discovery for… → …
A user asks for GitHub reference projects
SKILL.md covers Default workflow, Required local tools, Main command and Presets, plus 7 more sections
Runs JavaScript scripts from its folder; calls node, git and npm

What it does

Search Context is an agent skill from instructa/agent-skills. Find, clone, inspect, and summarize high-quality GitHub reference repositories for coding agents. Use when a user asks for GitHub reference projects, examples, prior art, inspiration, implementation patterns, or includes "$search-context" in a coding prompt.

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 21 other files, including scripts and reference files (for example `README.md`, `agents/openai.yaml` and `examples/example-ios-progress-ring-output.md`).

It sits in Mobile, covering Intellectual property and iOS development. It works with GitHub and iOS. The repository describes itself as: A curated collection of agent-skills. The licence is MIT.

When your agent uses it

A user asks for GitHub reference projects
Implementation patterns
Includes $search-context in a coding prompt

Example prompts

“$search-context”
“/search-context”

Requirements

Node.js

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

Convert the user request into concise GitHub search phrases. For broad app/product requests, split the request into stack, domain, and…
If the user asks for local/third-party references, search the local reference library first.
Use GitHub repository discovery for fresh references, not GitHub code search.
Prefer recent, maintained, readable repositories.
Clone only the top candidate pool using blobless shallow clone.
Inspect local and cloned repositories with rg.
Verify candidates with local proof terms and reject generic/noisy references.
Write a compact Markdown reference manifest with rejected/noisy references.
Tell the agent which files are worth reading and why.

What it can do on your machine

Read from SKILL.md and the folder at commit d49c149. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (JavaScript, from the files we listed), which the agent can run.
Shell commands in SKILL.md call:
- node
- git
- npm
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, npm and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Search Context loads about 2.1k tokens when it runs, and up to ~2.7k if it reads all its reference files. Until then it costs about 68 tokens; SKILL.md has 967 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~68
When it runs · the whole SKILL.md, loaded when a task matches: ~2.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~2.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from instructa/agent-skills at commit d49c149, republished under its MIT licence (© instructa). 967 words, ~2,074 tokens.

Download SKILL.mdSave it as .claude/skills/search-context/SKILL.md (or your agent's skills folder). This skill also uses 16 other files; get the full folder from GitHub.

name: search-context
description: Find, clone, inspect, and summarize high-quality GitHub reference repositories for coding agents. Use when a user asks for GitHub reference projects, examples, prior art, inspiration, implementation patterns, or includes "$search-context" in a coding prompt.
license: MIT
metadata.version: 0.1.0
metadata.requires: gh, git, rg, node

Search Context

Use this skill when the user wants an agent to find useful GitHub reference projects for a feature, UI pattern, implementation pattern, platform, framework, or library.

Trigger examples:

$search-context visual progress indicator ring for ios app latest 2026
find GitHub references for a SwiftUI circular progress ring
how do good projects implement this pattern?
clone a few reference repos and tell me which files to inspect
give this agent GitHub context before implementing the feature

The goal is not faster raw code search. The goal is better reference selection, fewer cloned repositories, less context noise, and a clean manifest that tells the coding agent what to inspect.

Default workflow

Convert the user request into concise GitHub search phrases. For broad app/product requests, split the request into stack, domain, and pattern facets instead of running one overloaded query.
If the user asks for local/third-party references, search the local reference library first.
Use GitHub repository discovery for fresh references, not GitHub code search.
Prefer recent, maintained, readable repositories.
Clone only the top candidate pool using blobless shallow clone.
Inspect local and cloned repositories with rg.
Verify candidates with local proof terms and reject generic/noisy references.
Write a compact Markdown reference manifest with rejected/noisy references.
Tell the agent which files are worth reading and why.

Required local tools

This skill expects these tools to be available in the shell:

gh, authenticated with GitHub
git
rg, also known as ripgrep
node version 18 or newer

Before running a search, use:

bash

node scripts/search-context.mjs check

Main command

From the skill directory:

bash

node scripts/search-context.mjs run "visual progress indicator ring for ios app latest 2026" \
  --preset ios-swift \
  --max-repos 5

If the package has been linked with npm link, use:

bash

search-context run "visual progress indicator ring for ios app latest 2026" --preset ios-swift

Presets

Use a preset when the platform or stack is clear.

ios-swift: iOS, Swift, SwiftUI, UIKit, Apple UI components.
web-react: React, Next.js, Vite, Tailwind, component patterns.
generic: fallback when the stack is unknown.

The preset controls GitHub language filters, query expansion, local rg terms, file globs, and scoring hints. Presets are hints, not the whole plan: broad requests should still be decomposed into narrower searches such as framework architecture, domain examples, and UI/workflow patterns.

Local reference library

Use the local library for existing third-party folders or previously curated references:

bash

node scripts/search-context.mjs library add ../third-party/some-repo --tags react,ui --presets web-react --project current
node scripts/search-context.mjs library search "ProgressRing"
node scripts/search-context.mjs run "React progress ring" --sources library,github --project current

Library metadata is stored in the OS user cache at <cache>/library/repositories.json. Project-specific clusters are stored in the same registry when --project current or --project <id> is used.

Keep FFF or any future long-lived index as an optional search backend under this library workflow. Do not make FFF a hard requirement and do not split this into a separate skill unless the goal changes from reference selection to general code search.

Clone policy

Use blobless shallow clones for reference repositories:

bash

git clone --depth=1 --filter=blob:none --single-branch --no-tags <repo-url> <user-cache>/search-context/refs/owner__repo

Do not use normal full clones by default. Do not clone more than 5 repositories unless the user explicitly asks. Do not install dependencies from cloned reference repos. Do not execute cloned project code. Do not copy large code blocks into the agent context.

By default, keep cloned repositories and manifests in the OS user cache, not in the current project. Use --project-local only when the user explicitly wants .refs/ and .context/ in the current directory. Inside a Git worktree, those project-local paths must be ignored or the CLI will refuse to write them.

Show full SKILL.md (432 more words)Show less

Search policy

Use repository discovery first. Avoid using gh search code as the primary source. Use local rg after cloning to verify that the repository actually contains relevant implementation files. GitHub Code Search can be used as an optional pre-clone proof gate, but do not depend on it by default because the API is rate-limited.

Good reference selection beats raw search speed.

For mixed requests, prefer several narrow repository searches over one broad query. Example: "habit life app with TanStack Start" should produce stack queries like tanstack start, domain queries like habit life, and pattern queries like habit life tanstack start. Do not let a general React preset drown the run in unrelated component libraries.

Proof gates should reject or down-rank candidates that only match generic terms like react, start, or full. For known stacks/domains, require concrete code proof where possible:

TanStack Start: @tanstack/react-start, createServerFn, StartServer, StartClient, routeTree.gen, vinxi.
Habit apps: habit, streak, completion, calendar, routine.
Noise: raw GitHub zip links, default secrets, and README-only bait.

Score repositories by:

intent match
language and stack match
recent pushed_at
not archived
not a fork unless explicitly useful
readable size
license presence
examples, demos, samples, or preview apps
local matches in relevant implementation files

Output contract

Always produce a Markdown manifest. The default output is:

text

<user-cache>/search-context/runs/<timestamp>/reference-context.md

The manifest must include:

user goal
preset used
search plan mode and facets, when generated
GitHub search phrases used
top reference repositories
why each repository is useful
local path for each cloned repository
relevant files with short snippets only
rejected references with short reasons
what to study
what not to copy
any failures or uncertainty

Do not dump full repositories or long file contents into the response.

Recommended agent behavior after the manifest

After the manifest is written, the coding agent should:

Open only the relevant files listed in the manifest.
Study implementation patterns, API choices, animation structure, state handling, and styling.
Adapt the pattern to the current project.
Respect licensing and avoid copying large sections of code.
Implement the requested feature in the user's project.
Run tests or build checks if available.

Useful commands

Run a reference search:

bash

node scripts/search-context.mjs run "SwiftUI progress ring animation" --preset ios-swift

Preview searches without cloning:

bash

node scripts/search-context.mjs run "SwiftUI progress ring animation" --preset ios-swift --dry-run

Use SSH for cloning:

bash

node scripts/search-context.mjs run "SwiftUI progress ring animation" --preset ios-swift --ssh

Search the local reference library:

bash

node scripts/search-context.mjs library search "Circle().trim"

Clean cached reference repos older than 30 days:

bash

node scripts/search-context.mjs clean --older-than 30d

Safety and licensing

Treat cloned repositories as untrusted code. Never run project scripts, package managers, tests, binaries, or install commands inside a reference repository unless the user explicitly asks and the risk is understood. Use reference repos for ideas, structure, and comparison, not for blind copying. Surface license information in the manifest when available.

Files

SKILL.md and 16 other files (scripts, references) in skills/engineering/search-context of instructa/agent-skills.

SKILL.md
.gitignore
LICENSE
README.md
VERSION
agents/openai.yaml
examples/example-ios-progress-ring-output.md
examples/usage.md
package.json
presets/generic.json
presets/ios-swift.json
presets/web-react.json
references/security.md
references/workflow.md
scripts/search-context.mjs
templates
… and 1 more

Open the folder on GitHubat commit d49c149

Compare with similar skills

Search Context next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Search Context compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Search Context this skillinstructa/agent-skills	139	—	~2.1k	Automated safety check: Pass	MIT	9 days ago
iOS App Store SubmitZestfulPulse/ios-app-store-submit	142	—	~4.7k	Automated safety check: Pass	MIT	6 days ago
Web To Mobilesuntay44/web-to-mobile-magic-plugin	107	—	~781	Automated safety check: Pass	MIT	24 days ago
Swift Developmentaiskillstore/marketplace	430	—	~1.8k	Automated safety check: Pass	None	today
Reviewing Changesbitwarden/ios	694	—	~1.1k	Automated safety check: Pass	GPL-3.0	yesterday
iOS SecurityHoangNguyen0403/agent-skills-standard	570	—	~500	Automated safety check: Pass	MIT	yesterday

Similar skills

iOS App Store Submit
ZestfulPulse/ios-app-store-submit
Build, sign, and submit a Flutter/iOS app to the App Store Connect — covers Xcode archive/export, code signing (including headless-Mac keychain workarounds), the asc CLI for App Store Connect…
142 GitHub stars~4.7k tokensUpdated 6 days ago
MobileAuto-check passed
Web To Mobile
suntay44/web-to-mobile-magic-plugin
Orchestrate website or web app conversion into a mobile app.
107 GitHub stars~781 tokensUpdated 24 days ago
MobileAuto-check passed
Swift Development
aiskillstore/marketplace
Comprehensive Swift development for building, testing, and deploying iOS/macOS applications.
430 GitHub stars~1.8k tokensUpdated today
MobileAuto-check passed
Reviewing Changes
bitwarden/ios
Official
Performs comprehensive code reviews for Bitwarden iOS projects, verifying architecture compliance, style guidelines, compilation safety, test coverage, and security requirements.
694 GitHub stars~1.1k tokensUpdated yesterday
DevelopmentAuto-check passed
iOS Security
HoangNguyen0403/agent-skills-standard
Secure iOS apps with secure storage, biometrics, and data protection.
570 GitHub stars~500 tokensUpdated yesterday
MobileAuto-check passed
Orca iOS Simulator Control
stablyai/orca
iOS Simulator control from inside Orca, with the live device view in Orca's emulator pane. Use when driving a booted Apple Simulator on macOS: taps, gestures…
87k GitHub starsUsed in 1 repo~584 tokens
MobileAuto-check passed

More from instructa/agent-skills

All 17 skills in this repo

App Spec Packager
instructa/agent-skills
A skill your agent uses when the user wants to turn an application, product, startup idea, SaaS, mobile app, web app, API, AI product, or internal tool into a production-ready Markdown specification…
139 GitHub stars~1.5k tokensUpdated 9 days ago
Auto-check passed
Codex Reviewer
instructa/agent-skills
Have Codex review a feature or change from Claude Code, then let Claude address the findings and request verification.
139 GitHub stars~1.6k tokensUpdated 9 days ago
Auto-check passed
Secleak Check
instructa/agent-skills
Run or install repo security leak checks with BetterLeaks and Trivy.
139 GitHub stars~557 tokensUpdated 9 days ago
Auto-check passed
Delegate Fable
instructa/agent-skills
Delegate a bounded task from a Codex session to a Fable-powered Cursor Agent in the same Herdr workspace, then wait for and collect the result.
139 GitHub stars~925 tokensUpdated 9 days ago
Auto-check passed
Delegate Grok
instructa/agent-skills
Delegate a bounded task from a Codex session to Grok 4.6 with xhigh reasoning in the same Herdr workspace, then wait for and collect the result.
139 GitHub stars~951 tokensUpdated 9 days ago
Auto-check passed
Delegate Sol
instructa/agent-skills
Delegate a bounded task from a Codex session to GPT-5.6 Sol in the same Herdr workspace, then wait for and collect the result.
139 GitHub stars~1.2k tokensUpdated 9 days ago
Auto-check passed

Works with

Questions about Search Context

What does Search Context do?

Find, clone, inspect, and summarize high-quality GitHub reference repositories for coding agents. Search Context is an agent skill from instructa/agent-skills. Find, clone, inspect, and summarize high-quality GitHub reference repositories for coding agents.

When should I use Search Context?

Search Context fits situations like: A user asks for GitHub reference projects; implementation patterns; includes $search-context in a coding prompt.

How do I install Search Context in Claude Code?

Run `npx skills add instructa/agent-skills --skill search-context -a claude-code`. Or copy the skill folder (skills/engineering/search-context in instructa/agent-skills) into .claude/skills/search-context in your project. Claude Code loads it when a task matches its description.

How do I install Search Context in Codex?

Run `npx skills add instructa/agent-skills --skill search-context -a codex`. Or copy the skill folder (skills/engineering/search-context in instructa/agent-skills) into .agents/skills/search-context in your project. Codex loads it when a task matches its description.

Can I use Search Context in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add instructa/agent-skills --skill search-context -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/search-context, .gemini/skills/search-context, .github/skills/search-context and .opencode/skills/search-context in your project.

What does Search Context need to run?

Going by SKILL.md and its folder, Search Context needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node, git, npm and gh). Our summary lists: Node.js.

Does Search Context access the network?

SKILL.md contains no URLs. Its commands use git, npm and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Search Context safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Search Context use?

Search Context is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Search Context use?

About 2.1k tokens (SKILL.md is roughly 8.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 617 tokens, read only when the agent opens those files.

What are the alternatives to Search Context?

Skills that share tags, products or a category with Search Context: iOS App Store Submit (ZestfulPulse/ios-app-store-submit, 142 stars), Web To Mobile (suntay44/web-to-mobile-magic-plugin, 107 stars), Swift Development (aiskillstore/marketplace, 430 stars) and Reviewing Changes (bitwarden/ios, 694 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Search Context?

instructa (a GitHub organization) maintains it in instructa/agent-skills, which has 139 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on September 28, 2026.

Source: instructa/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Search Context

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Search Context

Default workflow

Required local tools

Main command

Presets

Local reference library

Clone policy

Search policy

Output contract

Recommended agent behavior after the manifest

Useful commands

Safety and licensing

Files

Compare with similar skills

Similar skills

More from instructa/agent-skills

Related

Questions about Search Context