agentleFS
Sign inStart free
deepakkambojdeepakkamboj/personal-assistant-skills/.github/copilot-instructions.md

personal-assistant-skills

Copilot instructions1 starsChanged 2 months agoMITView on GitHub

This repository uses a vendor-neutral .agents/ agent system as the single source of truth. Read .agents/AGENTS.md first. Skills are discovered from .agents/skills/<skill>/SKILL.md. Key conventions: - Configuration is a single config.json resolved from the ASSISTANT_CONFIG environment variable (fallback ~/.assistant/config.json), plus a content.md companion for prose, voice samples, and prompts. There is no data/ folder. - Email (Gmail), calendar, and LinkedIn publishing/fetching are provided by the connected-workspace MCP server (.agents/mcp/connected-workspace.json). Prefer those MCP tools over writing new scripts for those capabilities. -…

The file

We split this copilot-instructions.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every skill is a folder with a SKILL.md (YAML frontmatter).

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 3,779 Copilot instructions files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
copilot-instructions.md

GitHub Copilot — Repository Instructions

This repository uses a vendor-neutral .agents/ agent system as the single source of truth.

Read .agents/AGENTS.md first. Skills are discovered from .agents/skills/<skill>/SKILL.md.

Key conventions:

  • Configuration is a single config.json resolved from the ASSISTANT_CONFIG environment variable (fallback ~/.assistant/config.json), plus a content.md companion for prose, voice samples, and prompts. There is no data/ folder.
  • Email (Gmail), calendar, and LinkedIn publishing/fetching are provided by the connected-workspace MCP server (.agents/mcp/connected-workspace.json). Prefer those MCP tools over writing new scripts for those capabilities.
  • Shared artifact templates live in .agents/templates/.
  • Every skill is a folder with a SKILL.md (YAML frontmatter). Do not add skill.json.
  • Skills are invocable as slash commands via prompt files in .github/prompts/ (e.g. /assistant-me, /assistant-linkedin, /assistant-post, /assistant-ai-digest). Each prompt just points at the canonical SKILL.md; enable them with the chat.promptFiles VS Code setting. (Claude Code uses the /assistant:<name> form.)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free