devflow:knowledge-management

You can automatically route documents to Confluence, Google Drive, or RAG memory by providing the content and a target destination. The skill intelligently routes the ingested URL, file, or raw text while enforcing safety checks and user consent before creating or updating documents.

The best way to ingest external URLs and raw text into a knowledge base is to specify your content and target backend. The skill handles the ingestion process with pre- and post-ingest validation, ensuring data is correctly persisted to RAG Memory, Confluence, or Google Drive.

Yes, you need explicit user consent before creating or updating documents in Confluence or Google Drive. The skill enforces safety checks and requires clear actor identification along with backend configuration and a defined collection or folder target before proceeding.

Yes, you can ingest files into RAG memory while enforcing access error guardrails. The skill supports ingesting URLs, files, or raw text and includes built-in guardrails for backend availability and access errors to ensure safe knowledge persistence.

If backend configuration or collection targets are missing during knowledge ingestion, the process will fail validation. The skill requires a defined collection or folder target from list_collections and user input, along with clear actor identification, to route and persist information correctly.

No, knowledge management routing does not work without specifying a folder target in Google Drive. The skill requires a defined collection or folder target from user input and list_collections to successfully persist information to the configured backend.