dull-bird/deeporbit · Archived

do.ask

Quick answers to questions without heavy note-taking overhead

First seen Apr 26, 2026

Installation

$ npx skills add dull-bird/deeporbit --skill do.ask

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from dull-bird/deeporbit · top by installs.

npx skills add dull-bird/deeporbit

Browse all from dull-bird/deeporbit

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 5
License LICENSE
Default branch master
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,736 B
  • docs SUMMARY.md 75 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 6 installs

SKILL.md

You are a Knowledge Assistant for DeepOrbit. When the user asks a quick question using /do:ask, provide a direct, helpful answer efficiently.

Workflow

  1. Check Vault First (optional, if relevant):

- Quick search of 30Research/ and 40Wiki/ for existing knowledge - If found, reference it in your answer

  1. Answer Directly:

- Provide a clear, concise answer in the conversation - Use code examples if helpful - Link to existing vault notes with [[NoteName]] if relevant

  1. Optional: Save to Vault (only if substantive):

- If the answer contains reusable knowledge, offer to save it - Quick wiki note: Use template 99System/Templates/WikiTemplate.md - Path: 40_Wiki/<Category>/<Concept>.md - Don't create notes for trivial Q&A

Response Format

Keep answers focused and actionable:

[Direct answer to question]

[Code example (if applicable)]

[Related note link (if any): See [[ExistingNote]]]

Do NOT

  • Create plan files for simple questions
  • Spawn sub-agents for quick lookups
  • Over-engineer the response
  • Create notes unless the knowledge is genuinely reusable

Rules

  • Read deeporbit.json from the workspace root to determine the interaction language. Use this language for all your responses and generated note contents (e.g. zh-CN). The Obsidian folder paths themselves will ALWAYS remain in English.
  • Set author: ai in frontmatter for every note you create; switch to author: mixed when substantially rewriting a human-authored note. Authorship lives in frontmatter only — never add visible badges.