Help with the team wiki

A team wiki is useful only if people can find the right information. An Agent can help answer questions and keep pages clear.

This example uses Confluence through an MCP connection, which lets Fluso use another app's tools. The available actions depend on that connection and your account.

Start with a question

Add the connection under Plugins → MCP. Select it for the Agent.

"Help our team find answers in Confluence. Read the relevant pages and link to the source. If pages disagree, point that out instead of choosing an answer for us."

Try a question with an answer you can check:

"Where should a new colleague put customer meeting notes? Show me the page that explains it."

Improve a page

Once it can find the right material, give it a specific edit:

"Make this team's home page easier for a new colleague to use. Explain where documents belong and keep the existing links and activity sections."

Read the proposed changes before you expand the work to other pages. Page edits need write access and follow your approval settings.

Teach it the team's method

If you repeat the same guidance, ask Manager to save it as a skill. A skill is a reusable set of instructions, with supporting files when needed.

"Save our approach to wiki updates as a skill. Read the page first, preserve useful sections, and check the links after editing. Use it for this Agent."

Check that the Agent's selected skills include it. A skill does not grant access to an app.

When several Agents use the same skill

Custom skills are shared files in your workspace. Editing one can affect other Agents that use it.

Ask for a separate skill if the change should apply only to this Agent. Keep account credentials out of the skill's instructions and files.

You can include a custom skill when you share an Agent. Review the whole folder before sharing.

What about a job such as making phone calls?

An Agent can use other services when you provide a working integration and account access. Calling is not built into every Agent.

For example, a phone briefing needs a calling provider, a connected account, and your permission to call the chosen number.

After you confirm that setup works:

"Prepare a brief for each confirmed meeting tomorrow. Call my number ten minutes before it starts and keep the briefing under two minutes."

Agree what information it may say aloud and whether it may leave voicemail. A request accepted by the provider does not prove you heard the call.

Check scheduled calls when meetings move. Routines check at set times, so approvals, other work, and service failures can delay them. Keep a written brief available too.