Skip to content
Docs

Skills and methods

A skill is a plain-language playbook for one kind of task: how to research an account, draft a cold email, prepare a meeting brief, or write a LinkedIn post. When you ask for work, Dija picks the skill that fits and runs a job following its steps. Your team can customize any built-in skill or add new ones.

Methods

A method is a collection of skills for one discipline, managed under Methods on Connections:

  • Dija basics: Included with every workspace and cannot be removed. It guides initial setup, drafts your Company brain from your website, learns how you and your team really write, sends the morning daily brief, learns how your workspace uses newly connected tools, turns how you do a piece of work into a skill of your own, and tidies shared memory (see Schedules and the daily brief).
  • Dija sales method: Researches target companies, finds buying contacts, qualifies accounts against your ICP, drafts outbound sequences, handles replies, prepares meeting briefs and writes the follow-up afterwards, watches your open deals for the daily brief, reviews a deal or the whole pipeline for a forecast, and refines your ICP from results.
  • Dija marketing method: Defines target audiences, finds and pitches creator, newsletter, and community partners, joins relevant community threads, writes posts, keeps a sourced note on each competitor, plans a launch backward from its date, and follows up with new product sign-ups.

Methods require no credentials of their own; they run on whichever tools your workspace has connected. Opening a method shows its skills grouped under Ready and Needs a tool (with links to connect missing categories), and its tile summarizes readiness (such as "4 of 6 ready · needs a calendar").

Only the workspace owner adds or removes methods. If you ask for work covered by an uninstalled method, Dija offers it in chat (or notifies the owner if you are not the owner). Removing a method stops future jobs and schedules from using its skills, while keeping past jobs and your custom skill notes intact.

Tool manuals

Every integration in the directory includes a tool manual named "working in <tool>" (for example, working-in-hubspot), explaining how that vendor organizes records, what fields to populate or log, and what not to touch. Jobs load the relevant tool manual alongside the task skill; Dija never starts a job with a tool manual alone when a task skill applies.

Customizing a skill for your company

Tell Dija in plain words how your team handles a workflow, such as "From now on, keep first emails under 90 words and never mention pricing". Dija saves your custom instructions alongside the built-in skill under Memory > Skills, with full version history that managers and the owner can restore anytime (see Memory).

From then on, every job of that type follows your instructions wherever they differ from the built-in skill, while improvements to Dija's built-in skill continue arriving underneath.

Custom skill instructions shape how work is drafted and researched, never security controls: they cannot approve actions, create or lift rules, bypass Do not contact, or alter when Dija selects a skill.

Writing new skills and importing plugins

  • Write a skill in chat: For a workflow no existing skill covers, show Dija the work once or describe the last time you did it, then say "Make this a skill". Dija confirms the steps with you in one message, saves it as a standalone company skill (single text up to 8,000 characters), and tries it on a case whose right answer you already know before anyone relies on it. A member's skill is tried first and then proposed for a manager or the owner to approve.
  • Import a plugin folder: For multi-file skills or bundled MCP integrations, the workspace owner can open Connections > Your own, click Add your own, and choose A plugin folder. Upload a folder formatted for Dija, Claude, or OpenAI containing its plugin manifest and SKILL.md files (in the open Agent Skills format). Imported skills appear under Methods, HTTP MCP servers appear under Your own, and unsupported components (local stdio servers, hooks, or scripts) are skipped and listed on screen. An imported skill with the same name as a built-in skill replaces it for your workspace.

Who can add or edit skills

ActionWho can do it
Add, import, or remove a method or plugin folderWorkspace owner only (Dija never installs methods or plugins on its own)
Save custom skill instructions or write a new skill in chatManagers and owner immediately; members submit a proposal for manager or owner approval
Request skill changes on a phone call or external assistantAlways saved as a written proposal for approval (see Approvals and rules)
Improvements suggested by Dija after repeated editsProposed for a manager or the owner to review