zrosenfield/ingest-knowledge
Skills/knowledge/ingest-knowledge/SKILL.md
Extracts tacit knowledge from any input — typed text, transcripts, emails, documents, or Slack threads — and writes it into the Knowledge Base library as structured markdown. Triggers when someone shares knowledge directly, pastes content, or uploads a file to the Submissions library. Resolves matching open Knowledge Gaps items automatically.
$ install --global
skillsauthnpx skillsauth add zrosenfield/sharepoint-ai-skills ingest-knowledgeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 23, 2026, 1:18 PM8.2s1 file scanned
SKILL.md
- name:
- ingest-knowledge
- description:
- Extracts tacit knowledge from any input — typed text, transcripts, emails, documents, or Slack threads — and writes it into the Knowledge Base library as structured markdown. Triggers when someone shares knowledge directly, pastes content, or uploads a file to the Submissions library. Resolves matching open Knowledge Gaps items automatically.
When someone shares knowledge — typed, pasted, or by uploading a file to the Submissions library — extract tacit knowledge and add it to the Knowledge Base.
What to Extract
Listen for more than facts. Actively look for:
- Decisions and their reasoning ("we went with X because...")
- Tradeoffs acknowledged ("the downside is..." / "we accepted that risk because...")
- Failed approaches ("we tried X and it didn't work because...")
- Changes over time ("we used to do X, then switched to Y when...")
- Edge cases and exceptions ("that works except when..." / "watch out for...")
- Unwritten rules ("technically the policy says X but in practice we...")
- Lessons learned ("if I had to do it again..." / "the thing nobody tells you is...")
How to Structure It
- Check the Knowledge Base library for an existing file on this topic.
- If a file exists, read it. Add new knowledge under the right heading. If the new information updates, contradicts, or adds context to existing content, note the change — don't silently overwrite. Add a new subsection or append under the existing one.
- If no file exists, create a new markdown file named with a short slug (e.g., vendor-contracts.md).
- For each piece of knowledge, use the sections that apply:
- Current State — what's true now
- Rationale — why it's this way
- History — what came before or changed
- Nuance — edge cases, exceptions, gotchas
- Always include the Source line (who, when, what format), Added date, and Last Verified date (set to today).
- After ingesting, check the Knowledge Gaps list for Open or Assigned items this knowledge answers. Update matching items: set Status to Resolved, Resolved Date to today, KB File to the filename, and Source Type to match the input format (Transcript, Email, Document, Slack, or Typed).
- If the new knowledge updates an existing KB entry, also update that entry's Last Verified date to today.
When processing transcripts or meeting notes, preserve the conversational context that reveals reasoning. "Dana said we switched to CrowdStrike after the Meridian incident" is more valuable than "Pen testing vendor: CrowdStrike."
Related Skills
zrosenfield/Skills/writing/review-council
testing
VerifiedTrustedCommunity
--- name: review-council description: Convene a council of expert AI personas to review, stress-test, and improve any document, idea, proposal, or plan. Use this skill whenever the user asks to "review," "stress-test," "get feedback on," "critique," "poke holes in," "red team," "evaluate," "council," "panel review," or "get perspectives on" any content — whether it's an uploaded Word doc, Excel spreadsheet, PowerPoint deck, PDF, or just a raw idea typed into chat. Also trigger on phrases like "w
58SKILL.mdUpdated May 30, 2026
zrosenfield/scorecard-matrix
tools
VerifiedTrustedCommunity
Generates a polished, self-contained HTML heatmap scorecard — a weighted comparison matrix where entities (rows) are scored across dimensions (columns), with computed totals, rank badges, and a winner highlight. Use when asked to build a scorecard, comparison matrix, decision matrix, vendor evaluation, tool assessment, candidate scoring grid, competitive analysis, site-readiness matrix, or any weighted multi-criteria ranking. Interviews the user if entities or criteria are missing, constructs a validated JSON document, then renders it into a sandbox-safe HTML file using the component library. No external dependencies — output runs inside a SharePoint sandboxed iframe.
58SKILL.mdUpdated May 30, 2026
zrosenfield/roadmap-timeline
development
VerifiedTrustedCommunity
Generates a polished, self-contained HTML roadmap or milestone timeline from any project data — SharePoint lists, pasted tables, or a verbal description. Use when asked to build a project roadmap, product roadmap, migration timeline, release plan, onboarding sequence, run-of-show, phase plan, or any visual schedule showing items over time. Interviews the user if data is incomplete, constructs a validated JSON document, then renders it into a single sandbox-safe HTML file. Chooses between two layouts automatically: horizontal roadmap with swimlanes (for phase-range data) or vertical milestone list (for point-in-time events). No external dependencies — output runs inside a SharePoint sandboxed iframe.
58SKILL.mdUpdated May 30, 2026
zrosenfield/exec-report
development
VerifiedTrustedCommunity
Generates a polished, self-contained HTML executive report or dashboard from any data source — SharePoint lists, CSV exports, or a user description. Use when asked to build an exec report, one-pager, summary page, status dashboard, project summary, business review, or any single-page visual summary of data. Interviews the user if data is incomplete, constructs a validated JSON document block by block, then renders it into a single sandbox-safe HTML file using the component library. No external dependencies — output runs inside a SharePoint sandboxed iframe.
58SKILL.mdUpdated May 30, 2026