---
title: "Discussion on \"Agent knowledge is a trigger problem, not a writing problem\" | Hashnode"
description: "Discussion on \"Agent knowledge is a trigger problem, not a writing problem\". I put everything an agent needs to work in my framework into an MCP resource. Conventions, workflows, which files are generated, where secrets come from. It was accurate, it was complete, and it was o"
url: "https://hashnode.com/posts/agent-knowledge-is-a-trigger-problem-not-a-writing-problem/6a76fcb3e60de820b3f2d472"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Agent knowledge is a trigger problem, not a writing problem](https://tsdevstack.hashnode.dev/agent-knowledge-is-a-trigger-problem-not-a-writing-problem?utm_source=hashnode&utm_medium=feed)

I put everything an agent needs to work in my framework into an MCP resource. Conventions, workflows, which files are generated, where secrets come from. It was accurate, it was complete, and it was o

Aug 8 · 4 min read · tsdevstack.hashnode.dev  
Read the article

## Written by

[kramgyorgy](https://hashnode.com/@gyorgy)

@gyorgy · Amsterdam, Netherlands

  
[View profile](https://hashnode.com/@gyorgy)

Infrastructure as Framework for TypeScript microservices.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
