Skill This
AI Skill Report Card

Writing MangoApps Wiki Articles

A-83·Oct 5, 2026·Source: Web
Quick Start14 / 15

When the user describes a task's steps, immediately draft a wiki article using the template below. If no template has been provided yet, use the default, note that it's the default, and reuse whatever template is established for all future articles in the session without asking again.

Default template (use until the user supplies their own):

Markdown
# [Task Title]
Recommendation▾
Add an example showing a custom user-supplied template being adopted and reused, to demonstrate that specific workflow step in action
Overview

[1-2 sentence summary of what this article covers and why it matters]

Prerequisites
  • [Access/permissions needed]
  • [Tools or info needed]
Steps
  1. [Step one]
  2. [Step two]
  3. [Step three]
Notes / Tips
  • [Any gotchas, exceptions, or best practices]
Related Articles
  • [Links to related wiki pages, if any]
Workflow14 / 15

Progress:

  • Step 1: Confirm/collect the wiki template (ask once if not already provided; reuse thereafter)
  • Step 2: Get the task name and a one-line description of its purpose
  • Step 3: Collect the step-by-step process from the user (they will describe it)
  • Step 4: Ask only for missing essentials (prerequisites, permissions) — don't over-ask
  • Step 5: Draft the article, mapping content into the template sections
  • Step 6: Present the draft in a markdown code block, ready to paste into the MangoApps wiki editor
  • Step 7: Revise based on user feedback

Details:

  1. Template: If the user hasn't shared a template, use the default above and note "Using default template — share yours if you'd like a different structure." Once a custom template is given, save its structure and apply it to all future articles in the session.

  2. Task input: The user is the source of truth for steps — never invent MangoApps functionality, menu names, or UI details you weren't told. If a step is ambiguous or a gap exists (e.g., what happens after the last given step), ask a single clarifying question rather than guessing.

  3. Formatting for MangoApps wiki:

    • Use #/## headers (MangoApps wiki supports standard markdown/rich text)
    • Numbered lists for sequential steps, bullets for non-sequential info
    • Bold key UI elements the user mentions (e.g., Settings, Save)
    • Keep each step to one action per line — never combine two clicks into one numbered item
    • Add a "Notes/Tips" section for edge cases the user mentions in passing
    • If the user provides a MangoApps page URL (e.g., under rakata.mangoapps.com) for a related article, include it under "Related Articles"

  4. Output: Always deliver the finished article inside a fenced markdown code block so it can be copy-pasted directly into the MangoApps wiki editor at rakata.mangoapps.com.

Recommendation▾
Include a short example of revising a draft based on user feedback (Step 7) to fully illustrate the workflow loop
Examples16 / 20

Example 1: Input: "Make a wiki on how to submit a timesheet. Steps: go to Time & Attendance, click New Entry, pick the project, enter hours, click Submit."

Output:

Markdown
# How to Submit a Timesheet
Recommendation▾
Consider trimming slight redundancy between 'Best Practices' and 'Common Pitfalls' sections, as several points overlap (e.g., template reuse, no fabrication)
Overview

This article explains how to submit your weekly timesheet in MangoApps.

Prerequisites
  • Active MangoApps account
  • Assigned to a project
Steps
  1. Navigate to Time & Attendance.
  2. Click New Entry.
  3. Select the relevant project.
  4. Enter your hours worked.
  5. Click Submit.
Notes / Tips
  • Double-check the project selection before submitting — entries can't be edited after submission.
Related Articles
  • (add link if available)

**Example 2:**
Input: "Document how to reset a password. Only step I have: go to profile settings and click reset password."

Output: Draft the article with the one known step, and ask: "Is there a step after clicking 'Reset Password' — e.g., checking email or setting a new password — or does that trigger an external flow?" Then finalize once answered.
Best Practices
  • Never fabricate MangoApps features, menu names, button labels, or URLs — use exactly what the user states.
  • Keep steps atomic: one click/action per numbered line.
  • Reuse the confirmed template consistently across articles in the same session.
  • Bold UI elements to make the article scannable.
  • If the user gives steps out of order, reorder them logically before drafting.
  • When linking related articles, prefer actual rakata.mangoapps.com URLs the user supplies over placeholders.
Common Pitfalls
  • Don't guess at MangoApps UI details not provided by the user.
  • Don't skip the Overview/Prerequisites sections even if the user only gives raw steps — infer a short overview from context, but flag it as inferred if unsure.
  • Don't re-ask for the template every time once it's been established.
  • Don't bury multiple actions in a single numbered step.
  • Don't publish placeholder links as if they were real — mark them clearly as "(add link if available)" until a real URL is given.
0
Grade A-AI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
14/15
Workflow
14/15
Examples
16/20
Completeness
18/20
Format
14/15
Conciseness
13/15
Save to My Skills