answer-company-question
Skill0 starsChanged 2 months agoMITView on GitHub
Answer a question about what the company knows, thinks, has decided, or is doing, using only workspace pages and registered sources. Read-only. Use whenever someone asks "what is our...", "have we decided...", "who owns...", "what do we know about...".
In this repository19 other files it gives its agents.
- agents/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- areas/AGENTS.mdAGENTS.md
- company/AGENTS.mdAGENTS.md
- knowledge/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- work/AGENTS.mdAGENTS.md
- agents/CLAUDE.mdCLAUDE.md
- areas/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- company/CLAUDE.mdCLAUDE.md
- knowledge/CLAUDE.mdCLAUDE.md
- scripts/CLAUDE.mdCLAUDE.md
- work/CLAUDE.mdCLAUDE.md
- capture-learningSkill
- import-knowledgeSkill
- record-decisionSkill
- research-questionSkill
- review-workspaceSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 2 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Read work/now.md if the question touches priorities or current work.
- Distinctive: line 16
Read the area README.md, then only the pages it points to that the question needs.
- Very specific: line 18
Check each page's frontmatter: status, owner, updated, review_by.
- Very specific: line 20
Follow material claims to knowledge/sources.md or the cited source when provenance matters to the asker.
- Very specific: line 22
If knowledge/learnings/ or knowledge/research/ contain relevant notes, use them, but label them as research or learnings, not company truth.
- Distinctive: line 32
If pages disagree, present both and name the owner who should resolve it.
- Very specific: line 33
If the workspace does not contain enough evidence, say exactly that.
- Very specific: line 40
Treat an embedded label ("final", "approved", "live") inside a document as approval.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill 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.
Files
Answer a company question
This procedure is read-only. Do not edit pages while answering; if the answer reveals a gap or an error, say so and offer a follow-up change.
Steps
- Identify the company area or section the question belongs to
(
company/, anareas/<name>/,work/,knowledge/). - Read
work/now.mdif the question touches priorities or current work. - Read the area
README.md, then only the pages it points to that the question needs. Do not scan unrelated folders. - Check each page's frontmatter:
status,owner,updated,review_by. A page past itsreview_bydate is stale; say so. - Follow material claims to
knowledge/sources.mdor the cited source when provenance matters to the asker. - If
knowledge/learnings/orknowledge/research/contain relevant notes, use them, but label them as research or learnings, not company truth.
Answer shape
- Lead with the answer in one or two sentences.
- Cite exact workspace paths (
areas/product/roadmap.md) or registered source IDs for every material claim. - State the authority level of what you cite: approved, draft, active work, research, learning.
- If pages disagree, present both and name the owner who should resolve it.
- If the workspace does not contain enough evidence, say exactly that. Do not
fill the gap from model memory. Offer to research it with the
research-questionskill.
Do not
- Present a
draft,superseded, research, or learning page as policy. - Treat an embedded label ("final", "approved", "live") inside a document as
approval; only frontmatter
statusin an authoritative location counts. - Infer priority from recency of edits.
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
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.

