remember-interactive-programming — GitHub Copilot skill
Keeps the agent focused on live REPL exploration and the current system state. Useful for interactive programming, especially in Clojure.
npx skills add github/awesome-copilot --skill remember-interactive-programmingWhat remember-interactive-programming does
This skill frames the agent as an interactive programmer. The running system is treated as the source of truth, while the REPL is used to inspect that system and test changes before deciding what to edit. It fits workflows where the agent can work with a live REPL.
The prompt also asks the agent to briefly describe large evaluations that are hidden from the human, prefer structural editing tools for files, and keep its todo list current. The source calls out Clojure with REPL access as a strong use case, while the same idea can apply to another live-REPL setup. Install it when Copilot can reach the running system; without that access, the main behavior has little to act on.
What it helps with
- inspect the current program through a REPL
- test a proposed change against the running system
- tell the human what a large hidden evaluation is doing
- edit files with structural tools
- keep the todo list current
Example prompts for the agent
- Explore the current system through the REPL before deciding what to change.
- Evaluate this change in the REPL, then edit the file with a structural tool.
- Briefly describe the large evaluation you are running and tend the todo list.
How to install remember-interactive-programming
1Skills CLI (Vercel)
npx skills add github/awesome-copilot --skill remember-interactive-programming2GitHub CLI
gh skill install github/awesome-copilot remember-interactive-programming3Manually: put the files in place
.github/skills/remember-interactive-programming/SKILL.md1Skills CLI (Vercel)
npx skills add github/awesome-copilot --skill remember-interactive-programming -a claude-code2Manually: put the files in place
~/.claude/skills/remember-interactive-programming/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/remember-interactive-programming/
Manually: put the files in place
.agents/skills/remember-interactive-programming/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/remember-interactive-programming/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
Platform CLI
gemini skills install https://github.com/github/awesome-copilot --path skills/remember-interactive-programmingManually: put the files in place
.devin/skills/remember-interactive-programming/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set554
The whole set →Similar
Questions about remember-interactive-programming
How do I install remember-interactive-programming in GitHub Copilot?
Run npx skills add github/awesome-copilot --skill remember-interactive-programming. The skill file should be at .github/skills/remember-interactive-programming/SKILL.md.
What does remember-interactive-programming do?
It reminds the agent to inspect and modify the current system through a REPL, use structural file editing, and maintain its todo list. It also asks for a short explanation when a large evaluation is hidden from the human.
Why does this skill need a live REPL?
The REPL lets the agent inspect the current system and test changes against it. The source highlights Clojure with REPL access as a particularly suitable workflow.
Source text
SKILL.md · MIT
--- name: remember-interactive-programming description: 'A micro-prompt that reminds the agent that it is an interactive programmer. Works great in Clojure when Copilot has access to the REPL (probably via Backseat Driver). Will work with any system that has a live REPL that the agent can use. Adapt the prompt with any specific reminders in your workflow and/or workspace.' --- Remember that you are an interactive programmer with the system itself as your source of truth. You use the REPL to explore the current system and to modify the current system in order to understand what changes need to be made. Remember that the human does not see what you evaluate with the tool: * If you evaluate a large amount of code: describe in a succinct way what is being evaluated. When editing files you prefer to use the structural editing tools. Also remember to tend your todo list.
© github · MIT · github/awesome-copilot